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

Author	SHA1	Message	Date
Richard Belleville	7e7b4fd1a4	Fix breakage when built against protobuf head (#34945 ) This PR is required in order to upgrade to the `master` branch version of protobuf. To do this, we upgrade to the latest version of `rules_python` by: - Adding in explicit dependencies on all PyPi Bazel test dependencies - Resolving the circular dependency this creates for `xds-protos` by giving it a Bazel build - Generating the Python code for `xds-protos` as part of `generate-projects.sh` since doing so directly in Bazel would be highly fragily, dependent on many other projects' Bazel builds Closes #34945 PiperOrigin-RevId: 599875020	12 months ago
Richard Belleville	05aa736840	Fix bazel copyright notices (#26353 ) * Add copyright to Bazel files * Add check for copyright in Bazel files * Remove unintentional file	4 years ago
Lidi Zheng	025ebf7d07	Revert "Revert "[Aio] Add AsyncIO support to grpcio-status""	5 years ago
Lidi Zheng	82c586bb3c	Revert "[Aio] Add AsyncIO support to grpcio-status"	5 years ago
Lidi Zheng	95b4f22475	Add AsyncIO support to grpcio-status	5 years ago
Lidi Zheng	c34bef4ca4	Format all Bazel files with buildifier	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.	6 years ago
Lidi Zheng	45b3230ef2	Add grpcio-status extension package * The new package has 2 API `from_call` and `to_status` * Utilize the experimental API `abort_with_status` * Add 5 unit test cases	6 years ago