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

Commit Graph

Author	SHA1	Message	Date
Richard Belleville	786a3acab0	Add test	6 years ago
Richard Belleville	93d6344ac6	Add todo	6 years ago
Richard Belleville	dc8dba8afe	Add docstrings	6 years ago
Richard Belleville	8f1bfdab55	Yapf	6 years ago
Richard Belleville	b12299701d	Clean up logging	6 years ago
Richard Belleville	4c852bf25f	Cancel RPCs after a hash limit has been reached	6 years ago
Richard Belleville	b9cc2c210f	Explain how we take care of servicer threads	6 years ago
Richard Belleville	cdae8ca6ad	Add intro about algorithm	6 years ago
Richard Belleville	82aa4068c7	Elaborate on cancelling streaming RPCs	6 years ago
Richard Belleville	4ee154dd53	Elaborate on unary cancellation	6 years ago
Richard Belleville	c9e83db6bc	Implement streaming on the client side	6 years ago
Lidi Zheng	7b82924066	Update module import according to name changes	6 years ago
Richard Belleville	b6a5e94f71	Respond to ctrl+c on client side	6 years ago
Richard Belleville	244279cb36	Add client CLI	6 years ago
Lidi Zheng	aa567e5364	Adopt reviewer's advices	6 years ago
Lidi Zheng	5f98b1e8ef	Fix 2/3 str/bytes compatibility issue	6 years ago
Richard Belleville	b31431aea3	Switch over to a generator	6 years ago
Lidi Zheng	12c296b3dc	[Python] Add authentication extension example	6 years ago
Richard Belleville	7dccc07c2a	Start writing README	6 years ago
Richard Belleville	335e655a78	Free up server thread upon cancellation	6 years ago
Richard Belleville	32944fdeb2	Lay out bones of example	6 years ago
Richard Belleville	8fb51946bf	Fix multiprocessing example for MacOS. A closer reading of the API for getsockopt revealed that we were depending on an implementation detail of getsockopt on Linux. This assumption breaks down on MacOS. getsockopt merely guarantees that it will return on 0 in case of failure and a value greater than 0 in case of success. There is no guarantee as to which non-zero value you will receive. On Linux, it seems to be 1, the value which was explicitly set. On MacOS, it seems to be the value of the FLAG which was set, i.e. 512 for SO_REUSEPORT. This commit ensures the check we use does not rely on either of these implementation details.	6 years ago
Richard Belleville	624839b704	Add example Python server using compression.	6 years ago
Nicolas "Pixel" Noble	929f151016	Cherry-picking #19349 in.	6 years ago
Lidi Zheng	9bd526260a	Remove unused imports	6 years ago
Lidi Zheng	550dae1c47	Workaround the address contention issue	6 years ago
Nicolas "Pixel" Noble	0472933d71	Trying to fix build.	6 years ago
Lidi Zheng	559023c01d	Adopt reviewer's advice	6 years ago
Hao Nguyen	7f787bd083	Link against pthread in examples	6 years ago
Lidi Zheng	f7cb9c9f3e	Add Debug Example	6 years ago
Stanley Cheung	d30d538dba	Move math_server.js out of examples/ directory	6 years ago
Stanley Cheung	f04aabc0f3	PHP: update generated code tests	6 years ago
vam	db7fd70166	Fix examples (forgot to rename usages of the renamed target)	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	5391d8427e	Moar ipv6	6 years ago
Richard Belleville	aec0860ebf	Remove redundant line	6 years ago
Richard Belleville	1c65fd19e8	Fix wait_for_ready example for ipv4-only environments like Kokoro	6 years ago
Richard Belleville	4de4a7da7b	Reenable python bazel tests	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
Muxi Yan	f5262fe259	Update objc examples to use v2 API	6 years ago
Lidi Zheng	f062722c61	Adopt reviewer's advice * Use context manager to manage tcp socket * Rename tcp socket * Fix grammer error	6 years ago
Lidi Zheng	541cb00470	Add wait-for-ready example * With unit test * With Bazel integration * With REAME.md explaination	6 years ago
SataQiu	c99ac03b11	fix some spell errors	6 years ago
Prashant Jaikumar	4f2d8a0014	Fix bazel build for examples Fixed the bazel build for some code in the examples directory.	6 years ago
Lidi Zheng	7bb9e33d1a	Add one more import path for py_test	6 years ago
Lidi Zheng	93bab217be	Fix the import order to make hack work	6 years ago
Lidi Zheng	85bcce2e08	Fix typo in BUILD.bazel	6 years ago
Lidi Zheng	b3d907dce9	Explicitly depend on :grpcio	6 years ago

1 2 3 4 5 ...

755 Commits (9417b28bca22a6f86afc5cb1d22e71224e76f047)