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

Commit Graph

Author	SHA1	Message	Date
Prashant Jaikumar	f36e08e6dd	Add trace flag in cronet transport	6 years ago
Soheil Hassas Yeganeh	4080e7b65f	Retire the GRPC_ARENA_INIT_STRATEGY env variable. This is in the hot path and it is not needed anymore. Remove it for good.	6 years ago
Soheil Hassas Yeganeh	212e4b8657	Retire the GRPC_ARENA_INIT_STRATEGY env variable. This is in the hot path and it is not needed anymore. Remove it for good.	6 years ago
Richard Belleville	f900eec41d	Revert "Merge pull request #18727 from grpc/revert_compression" This reverts commit `8054a731d1`, reversing changes made to `c3d3cf8053`.	6 years ago
Richard Belleville	167540efd4	Revert "Merge pull request #18564 from grpc/compression" This reverts commit `9dfeb14be0`, reversing changes made to `7009f2df58`.	6 years ago
SataQiu	c99ac03b11	fix some spell errors	6 years ago
Richard Belleville	5afd77398e	Implement compression API within gRPC Python.	6 years ago
Doug Fawley	1ef874a03f	change from 400 to 415	6 years ago
Lidi Zheng	f931435f27	Update g_stands_for.md for v1.20.x	6 years ago
Lidi Zheng	b27131bcd7	Bump version to v1.21.0-dev	6 years ago
Lidi Zheng	c3215ea25b	Add per-platform details for GRPC_DNS_RESOLVER	6 years ago
Lidi Zheng	d1dc707908	Correct the default DNS resolver to ares	6 years ago
Lidi Zheng	a7b2ed3b98	Add documentation for 'grpcio-status' package	6 years ago
Doug Fawley	be014d005d	Misconfigured non-gRPC, HTTP/2 clients can sometimes connect to gRPC servers. Today, these clients will receive an HTTP status 200 (OK) with a trailer that gRPC clients would be able to interpret as an error, but non-gRPC clients would interpret as a success. In Go and Java, this will have a grpc-status of UNKNOWN due to an unexpected content-type header. In C, the content-type header is currently ignored, but a grpc-status of UNAVAILABLE will be returned if a handler for that method is not registered (which is likely in this scenario). This change updates the gRPC HTTP/2 spec to recommend returning HTTP status 400 (Bad Request) to interoperate better with non-gRPC clients. Note that we should not do any enforcement on user-agent, as the spec specifically says "the protocol does not require a user-agent to function".	6 years ago
Alexander Polcyn	2fe0d21736	Add a new compute engine channel creds interop test case	6 years ago
Mark D. Roth	2b03154cf4	Update naming doc.	6 years ago
Nicolas Noble	7dbe321d76	Update pending_api_cleanups.md	6 years ago
Yash Tibrewal	abcd5861eb	Nuking the poll-cv polling engine	6 years ago
Mark D. Roth	8878712aeb	Split client_channel tracer into two.	6 years ago
Nicolas Noble	fc56889a5c	Removing the change about headers, since it's the wrong file.	6 years ago
Nicolas Noble	0a36746ebe	Changing + to plus.	6 years ago
Nicolas Noble	e0059af33b	Adding a few potential breaking changes	6 years ago
Yash Tibrewal	394afb3a0c	Update validation rules for service config	6 years ago
Nguyen Hai Truong	029f6850c2	Remove duplicated word in document Although it is spelling mistakes, it might make an affects while reading. Signed-off-by: Nguyen Hai Truong <truongnh@vn.fujitsu.com>	6 years ago
Kim Bao Long	9e7bb5d17d	Remove duplicated word 'for for' in doc Although it is spelling mistakes, it might make an affects while reading. Co-Authored-By: Nguyen Phuong An <AnNP@vn.fujitsu.com> Signed-off-by: Kim Bao Long <longkb@vn.fujitsu.com>	6 years ago
Alexander Polcyn	85979e9a58	List c-ares tracers in documentation	6 years ago
Nguyen Hai Truong	9cf00ed80b	Reformat some link and fix typos Signed-off-by: Nguyen Hai Truong <truongnh@vn.fujitsu.com>	6 years ago
Nguyen Hai Truong	5c52622fa6	Trivial fix many typos Signed-off-by: Nguyen Hai Truong <truongnh@vn.fujitsu.com>	6 years ago
Vu Cong Tuan	69fab8eacb	Fix many typos in doc Signed-off-by: Vu Cong Tuan <tuanvc@vn.fujitsu.com>	6 years ago
Srini Polavarapu	d3313adecf	Bump version to v1.19.0-pre1	6 years ago
Srini Polavarapu	fb4ba97803	Bump version to v1.20.x	6 years ago
Jean de Klerk	1af046e723	docs: enumerate status codes in statuscodes.md statuscodes.md is one of the top search results for "grpc status codes", right behind codes.proto. Since this is a landing page for many people, and since the title and description of this page purports to be the generic status codes documentation page, it seems like a good idea to define terms before using them. Many people who are new to grpc/protobuf, for example, will be more accustomed to and choose markdown files over .proto files.	6 years ago
Christopher Warrington	dc2c81a78a	Copy edit keepalive documentation * Copy edits * Add additional blank lines before bulleted lists, which some Markdown parsers require.	6 years ago
Sanjay Pujare	a87d0fa8e2	Bump version to v1.18.x-pre1	6 years ago
Sanjay Pujare	d99f2f0307	Bump version to v1.19.x	6 years ago
Richard Belleville	dd4830eae8	Make gRPC version string available as grpc.__version__	6 years ago
Alexander Polcyn	a4e9f33b85	Add interop cloud to prod test for GoogleDefaultCredentials	6 years ago
Lidi Zheng	43599facf4	Channelz Python wrapper implementation * Expose the C-Core API in Cython layer * Handle the object translation * Create a separate package for Channelz specifically * Handle nullptr and raise exception if seen one * Translate C++ Channelz unit tests * Adding 5 more invalid query unit tests Adding peripheral utility for grpcio-channelz package * Add to `pylint_code.sh` * Add to Python build script * Add to artifact build script * Add to Bazel * Add to Sphinx module list	6 years ago
Srini Polavarapu	0adcbd5014	gRPC release schedule	6 years ago
Muxi Yan	f836319f1f	Bump version to v1.18.0-dev	6 years ago
Lidi Zheng	b1b669300f	Update Python documentation * Reorganize the section titles * Add Tutorial and Example	6 years ago
Alex Lo	f932b8e2d0	ipv6 addresses must be bracketed if using a port The host/port splitting code will not pull out a port if there are >=2 colons[1]. Unit test code demos this [2]. Note other documentation gets this right[3]. Example IP came from this issue[4] and the unit tests[2]. See also: relevant RFCs [5] [6] [1]`618a3f561d/src/core/lib/gpr/host_port.cc (L81)` [2]`618a3f561d/test/core/client_channel/resolvers/sockaddr_resolver_test.cc (L107)` [3]https://chromium.googlesource.com/external/github.com/grpc/grpc/+/chromium-deps/2016-07-19/src/core/ext/client_config/README.md [4]https://github.com/grpc/grpc/issues/6623 [5]http://www.iana.org/go/rfc5952#section-6 [6]http://www.iana.org/go/rfc3986#section-3.2.3	6 years ago
Lidi Zheng	cabe8d8f10	New Python documentation generation * Use templates instead of generating them every time * Theme changed * Add grpc_* modules * APIs grouped * No documentation for class members without docstring * Add docstring for status code	6 years ago
Soheil Hassas Yeganeh	48e4a81b05	Remeve memset(0) from arena allocated memory. Callers are updated to properly initialize the memory. This behavior can be overridden using GRPC_ARENA_INIT_STRATEGY environment variable.	6 years ago
Doug Fawley	b63524639b	fix minor punctuation noticed when editor removed spaces at end of line	6 years ago
Doug Fawley	a62c530465	Add protocol handshake to 'READY' connectivity requirements When security is disabled, not waiting for the HTTP/2 handshake can lead to DoS-style behavior. For details, see: https://github.com/grpc/grpc-go/issues/954. This requirement will incur an extra half-RTT latency before the first RPC can be sent under plaintext, but this is negligible and unencrypted connections are rarer than secure ones. Under TLS, the server will effectively send its part of the HTTP/2 handshake along with its final TLS "server finished" message, which the client must wait for before transmitting any data securely. This means virtually no extra latency is incurred by this requirement. Go had attempted to separate "connection ready" with "connection successful" (Issue: https://github.com/grpc/grpc-go/issues/1444 PR: https://github.com/grpc/grpc-go/pull/1648). However, this is confusing to users and introduces an arbitrary distinction between these two events. It has led to several bugs in our reconnection logic (e.g.s https://github.com/grpc/grpc-go/pull/2380, https://github.com/grpc/grpc-go/pull/2391, https://github.com/grpc/grpc-go/pull/2392), due to the complexity, and it makes custom transports (https://github.com/grpc/proposal/pull/103) more difficult for users to implement. We are aware of some use cases (in particular, https://github.com/soheilhy/cmux) expecting the behavior of transmitting an RPC before the HTTP/2 handshake is completed. Before making behavior changes to implement this, we will reach out to our users to the best of our abilities.	6 years ago
Mark D. Roth	f85fd026e3	Client-side health checking support.	6 years ago
Mark D. Roth	7b48518f65	Move core docs to core subdir.	6 years ago
Jan Tattermusch	3977c30f47	add a note message length encoding	6 years ago
Jan Tattermusch	0295a4cf2e	update ssl-performance.md	6 years ago

1 2 3 4 5 ...

549 Commits (2787dedd7049370c642e9315af3adc41a962545c)