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

Commit Graph

Author	SHA1	Message	Date
Lidi Zheng	e6dffc6fbe	Adding three more AsyncIO examples * Channelz or Debug * Route guide * Wait for ready	4 years ago
Esun Kim	e7afadc255	Refactor examples BUILD files	4 years ago
Richard Belleville	a362c2566d	Revert examples	4 years ago
Richard Belleville	c128e61cf4	Format examples	4 years ago
Richard Belleville	828edcc67a	Use bazel imports instead of sys.path	4 years ago
Richard Belleville	dc9e20665e	Copy proto files instead of adding to sys.path	4 years ago
Richard Belleville	c2c5057e9d	Fix up examples	4 years ago
Lidi Zheng	c34bef4ca4	Format all Bazel files with buildifier	5 years ago
Richard Belleville	1444cd1dd3	Revert "Revert "Merge pull request #20097 from gnossen/dual_version_python_tests"" This reverts commit `24c562dbaa`.	5 years ago
Richard Belleville	24c562dbaa	Revert "Merge pull request #20097 from gnossen/dual_version_python_tests" This reverts commit `c9c847f334`, reversing changes made to `07ba4de392`.	5 years ago
Richard Belleville	27990a5541	Explicitly add python versions to examples.	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
Lidi Zheng	541cb00470	Add wait-for-ready example * With unit test * With Bazel integration * With REAME.md explaination	6 years ago
Jan Tattermusch	0f8a3aeeb7	install jq	6 years ago
Jan Tattermusch	b1dbf68373	update the docker image to netcore3 preview3	6 years ago
Jan Tattermusch	d0c42dec85	hotfix: download unreleased preview3	6 years ago
Jan Tattermusch	cfc2156665	add AspNetCore interop server	6 years ago
Jan Tattermusch	71ee19cb16	fix interop docker build	6 years ago
Matt Kwong	c2158edea4	Fix Dart interop tests by upgrading to Dart 2	7 years ago
Jakob Roland Andersen	cb36a2a92b	Use pre-built Dart docker image.	7 years ago
Jan Tattermusch	8d3f976fcb	fix sanity tests	7 years ago
Jakob Roland Andersen	c7dd4b4309	WIP: Add Dart support in interop	7 years ago

8 Commits (60a5e474b8cabefb39be9dd06e9c18fbc9a5e825)