Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Richard Belleville	b26b25113f	Make soruce file validation exact	5 years ago
Esun Kim	f88bd06ee5	Go UPB!	5 years ago
Richard Belleville	5fd25f3c7c	Refactor rule.	5 years ago
Muxi Yan	de3131016d	update BUILD following the new style	5 years ago
Lukacs T. Berki	e2ba3aa070	Update C++ code generation to work with Bazel 0.29 . The above Bazel version changes proto compilation slightly: some proto files are put into a `_virtual_imports` directory and thus `_get_include_directory` needs to be updated accordingly. Ideally, it would use instead the `ProtoInfo` provider to tease out the proto import directories, but that's a bit more intrusive change.	5 years ago
Richard Belleville	4f13303ec4	Validate length of deps in py_grpc_library	5 years ago
Richard Belleville	a77404ae6b	Add README to bazel test	5 years ago
Richard Belleville	3638167e40	Call grpc_python_deps() from grpc_deps().	5 years ago
Richard Belleville	e89096cdf2	AAAAAAAHHHHHH	5 years ago
Richard Belleville	f054bd73f4	Compensate for missing upb dependencies	5 years ago
Richard Belleville	835b3d3293	Copyright.	5 years ago
Richard Belleville	7b2c8c27b0	Separate py_grpc_library and py_proto_library. By popular demand, we'll now be offering separate py_grpc_library and py_proto_library targets sharing the same interface as within google3. This change necessitated some modifications to how we pull in our own Python-level dependencies and how we make those available to those pulling in our project via Bazel. There is now a grpc_python_deps() Bazel workspace rule that pulls in the appropriate dependencies, which should be called from the client project's WORKSPACE file. A test has been added to the bazel/test/ directory to verify that this behavior works as intended. It's worth noting that the protobuf repository's usage of Starlark bind() caused a great deal of trouble in ensuring that we could also pull in six. This change also required a change in the way generated proto code is imported in the channelz and health-check modules, as well as in their associated tests. We were importing them two different ways, each relative. This resulted in two different module objects being imported into the process, which were incompatible. I am not sure exactly what caused this behavior to begin, as this should have been possible before this PR. As a workaround, I am simply trying two different absolute imports and using the one that works. This should function both inside and outside of Bazel environments.	5 years ago
Tony Lu	44868ae12a	Starting a new branch with same changes from https://github.com/grpc/grpc/pull/19621	5 years ago
Esun Kim	44de9634f6	Update third_party/upb to the latest	5 years ago
Esun Kim	ded9f46c06	Refactored BUILD file to isolate cronet rules	5 years ago
Nicolas "Pixel" Noble	a4608cb373	Properly using upb's upstream.	5 years ago
Nicolas "Pixel" Noble	a1189961af	Another upb Windows change.	5 years ago
Nicolas "Pixel" Noble	685695f8bc	Trying one another fix for upb.	5 years ago
Nicolas "Pixel" Noble	43a8461c24	Rollbacking upb stuff.	5 years ago
Nicolas "Pixel" Noble	c4481f5538	Trying out my upb change.	5 years ago
Esun Kim	bd5ed4fddd	Move compiler targets from /BUILD to /src/compiler/BUILD	5 years ago
Nicolas "Pixel" Noble	170beff648	Upgrading absl submodule, in the hope this will make Windows RBE work.	5 years ago
Prashant Jaikumar	43628b286f	Update googletest version to v1.8.1 Bazel builds of test/cpp/end2end:end2end_test were failing on Mac OS with v1.8.0 due to missing gtest symbols. The issue is not seen in v1.8.1. A WORKSPACE file was added to gtest repo in 1.8.1, so gtest.BUILD can be removed.	6 years ago
Marcel Hlopko	ecf04ccf4d	Require ProtoInfo in attributes, not "proto"	6 years ago
Marcel Hlopko	49f0fb9035	Migrate from dep.proto to dep[ProtoInfo]	6 years ago
Jan Tattermusch	a3fd28bdbf	fix ubsan build for 0.26	6 years ago
Nicolas "Pixel" Noble	8de64087a3	Clean bazel 0.26 upgrade.	6 years ago
Nicolas "Pixel" Noble	63e2c91efe	New version of upb.	6 years ago
Nicolas "Pixel" Noble	1a3dd36c89	Upgrading to bazel 0.26.	6 years ago
Nicolas "Pixel" Noble	e360dd4f76	Upgrading to bazel 0.26.	6 years ago
Hao Nguyen	79f7abb45e	Update zlib dependency	6 years ago
Hao Nguyen	1ddaafd677	Update protobuf version	6 years ago
Jan Tattermusch	659f71099c	upgrade bazel toolchain to fix ubsan RBE build	6 years ago
Moiz Haidry	49e7f4b2e4	Added more rules to resolve deps	6 years ago
Moiz Haidry	4995670257	Add support to import envoy protos	6 years ago
Moiz Haidry	6c3e3aeb77	Removed git repo from WORKSPACE as that was the incorrect location. Added the code to grpc_deps.bzl instead	6 years ago
Keith Smiley	f131adf89c	Fix bazel incompatible changes When building grpc with the upcoming `--incompatible_depset_is_not_iterable` flag, these violations were found	6 years ago
vam	5c15471710	Fix generated files as input issue (generated files were supported neither as srcs nor as deps).	6 years ago
vam	4c0d9e2f6b	Fix well_known_protos issue	6 years ago
vam	4269ce08f4	Make cc_grpc_library compatible with native proto_library and cc_proto_library rules. This is needed to comply with bazel best practices (each proto file is first processed by proto_library: https://docs.bazel.build/versions/master/be/protocol-buffer.html#proto_library) and generally bring cc_grcp_library rule up to date with latest Bazel changes (the rule hasn't gotten much updates since 2016). Detailed description. Bazel has native `cc_proto_library` rule, but it does not have `cc_grpc_library`. The rule in cc_grpc_library in this repo seems like the best candidate. This change makes possible using `cc_grpc_library` to generate on grpc library, and consume protobuf protion as dependencies. The typical `BUILD.bazel` file configuraiton now should look like the following: ```python proto_library( name = "my_proto", srcs = ["my.proto"], ) cc_proto_library( name = "my_cc_proto", deps = [":my_proto"] ) cc_grpc_library( name = "my_cc_grpc", srcs = [":my_proto"], deps = [":my_cc_proto"] ) ``` This allows to decouple all thre phases: proto descriptors generation (`proto_library`), protobuf messages library creation (`cc_proto_library`), grpc library creatio (`cc_grpc_library`). Notice how `cc_grpc_library` depends on `proto_library` (as `src`) and on `cc_proto_library` (as `deps`). Currently cc_grpc_library is designed in a way that it encapsulates all of the above and directly accepts .proto files as srcs. The previous version (before this PR) of cc_proto_library was encapsulating all of the 3 phases inside single `cc_proto_library` and also was doing it manually (without relying on the native `cc_proto_library`). The `cc_proto_library` is kept backward-compatible with the old version.	6 years ago
Richard Belleville	930cec4e27	Revert "Merge pull request #18912 from grpc/revert-bazel-changes" This reverts commit `c9a259aa3a`, reversing changes made to `9c882bc725`.	6 years ago
Richard Belleville	50b5240d0a	Revert "Merge pull request #18859 from grpc/internal_py_proto_library" This reverts commit `5b720f19c1`, reversing changes made to `a64ae3c0d5`.	6 years ago
Richard Belleville	f371d95c47	Handle protos at root package level	6 years ago
Richard Belleville	05f37c8143	Remove dependency on pubref/rules_proto. This commit resolves #18331. This commit resolves #18256. This commit resolves... another TODO that apparently didn't have an associated github issue. We swap out pubref's implementation of py_proto_library with our own, which more closely mirrors the interface of the internal py_proto_library, taking the descriptor file output of a proto_library rule as input. One minor change in behavior was introduced for simplicity. When a py_proto_library depends on a proto_library with a source proto file in a subdirectory of the bazel package, the import module of the resultant python library will reflect the package, not the full directory of the proto file, including both the bazel package and the subdirectories, as pubref did previously. This behavior also more closely mirrors google internal behavior. This commit also introduces a slightly more stringent bazel format script. Buildifier on its own will not take care of long lines, but by running yapf first, we end up with a more legible file. At the moment, there is no sanity check associated with this formatter.	6 years ago
Keith Moyer	0468a803b4	Add missing sha256 for http_archive deps	6 years ago
Bill Feng	85100a780f	windows rbe for Kokoro CI	6 years ago
Alexander Polcyn	4ba81610ee	Revert "Update the upb submodule for proto.oneof fix in generated code." This reverts commit `2975571fd3`.	6 years ago
Vishal Powar	2975571fd3	Update the upb submodule for proto.oneof fix in generated code.	6 years ago
Richard Belleville	f3f6237e6d	Wrap long line	6 years ago
Richard Belleville	615c95ed5c	Mitigate #18256	6 years ago

... 5 6 7 8 9 ...

582 Commits (54b027d599774afb9bf8f29fb0c72720b9efb9d0)