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

Commit Graph

Author	SHA1	Message	Date
Yash Tibrewal	a9bee9b7ed	Make Pluck use the changes made in FinalizeResult	6 years ago
Muxi Yan	e023468e9a	some nit fixes	6 years ago
Muxi Yan	b22120f696	Test fix	6 years ago
Muxi Yan	c83ab56fe1	copy->mutableCopy	6 years ago
Muxi Yan	f4a77ce492	_call->_pipe	6 years ago
Muxi Yan	78c2176afc	Assign finished and canceled	6 years ago
Muxi Yan	b77203fdf5	Move blocks into varibles for readability	6 years ago
Muxi Yan	8d0cf9ec0a	clang-format	6 years ago
Muxi Yan	94d220d32c	Rename variable	6 years ago
Jan Tattermusch	0898074809	regenerate protos	6 years ago
Jan Tattermusch	bff1452e5e	mark as experimental	6 years ago
Soheil Hassas Yeganeh	1dd09321cd	Add a non-polymorphic variant to RefCounted. Using RefCounted<Child, NonPolymorphic> users can now build smart, ref-counted pointers without paying the costs of a vtable when it's possible.	6 years ago
Vishal Powar	9e66b470ed	Change the varible names that keep track of rr policy its state and resolution tracking to remove reference of the policy type (RR) - Change RoundRobin to Child and rr_ to child_ - Changing the function names to remove reference to RR. - Change 'grpclb' to 'xds' where parent policy is referenced.	6 years ago
Tommy Chen	644f6e28db	fixed if<space>	6 years ago
Tommy Chen	b0e5e6414e	added check for GRPC_ENABLE_FORK_SUPPORT in register_fork_handlers	6 years ago
Tommy Chen	a01eeb47d7	re-running tests, squashing commits	6 years ago
Srini Polavarapu	25cd16ae58	Regenerate projects	6 years ago
Vijay Pai	0e29d7b9bc	Properly clear metadata and other structs when reusing ServerContext	6 years ago
Alexander Polcyn	aac8b239a2	Avoid re-resolution after c-ares resolver has been shut down	6 years ago
Yihua Zhang	3fefdde3cc	remove ALTS shared resources	6 years ago
Soheil Hassas Yeganeh	1f6d3189a9	Fix data race in client_channel. Since retry_dispatched is next to the metadata bitfields, compiler will generate a 2 byte store when we set this bitfield. Move this field to the end of the structure to avoid such a data race. Fixes #16896	6 years ago
Muxi Yan	6873456fd9	Revert "Fix timer manager debug code"	6 years ago
Soheil Hassas Yeganeh	0831996388	Remove memset from call_data from gRPC server. This was missed due to an explicit memset(0) in init_call_elem.	6 years ago
Yihua Zhang	99d8216d06	create internal version of grpc_call_cancel.	6 years ago
Juanli Shen	ec4892b316	Revert RR policy update in xDS	6 years ago
Lidi Zheng	9b65b40247	Label wait-for-ready argument in multicallables as experimental	6 years ago
Muxi Yan	0960acd05a	clang-format	6 years ago
Muxi Yan	b8c9648f60	Directly calling logging function to prevent dead-stripping	6 years ago
Muxi Yan	04cef1fd19	Revert "Prevent dead-stripping by explicitly calling init" This reverts commit `d0539dcc36`.	6 years ago
Muxi Yan	d0539dcc36	Prevent dead-stripping by explicitly calling init	6 years ago
Yash Tibrewal	699c10386d	Add method to fail recv msg for hijacked rpcs	6 years ago
Richard Belleville	c477cb8597	Add missing transitive dependencies This commit resolves an interop test currently failing on master. Over the past couple of weeks, bazel-based tests have been introduced. The current setup does not appear to automatically handle transitive dependencies. Instead, transitive dependencies such as `requests` have been manually added to `requirements.bazel.txt`. It appears that the build server happened to have the dependencies of the `requests` library installed already, but later had a configuration wipe. This was compounded by the google-auth library erroneously reporting that the `requests` module itself was not installed. In fact, it was the transitive dependencies of `requests` that were not being installed by the build file. (third-order dependencies of our test) I consider this a quick fix to get the build passing. In the long run, we need to automatically resolve and install transitive dependencies in our bazel builds. Resolves: #17170	6 years ago
Guantao Liu	4f9bdf4e06	Enable SO_REUSEADDR in client sockets	6 years ago
Juanli Shen	2eff247b74	Update the RR policy when fallback is disabled	6 years ago
Muxi Yan	2895ee9b6a	clang-format	6 years ago
Muxi Yan	33022c9172	Introduce GRPCAssert	6 years ago
Richard Belleville	ecd9063424	Use single NullHandler for whole library I was trying to get a feel for what the rest of the python ecosystem does with its logging, so I looked into the top few libraries on pypi: urllib3 maintains a logger for not quite every module, but for each one that does heavy lifting. The logger name is `__name__`, and no handlers are registered for any module-level loggers, including NullHandler. Their documentation spells out how to configure logging for the library. They explicitly configure a library root-level logger called `urllib3` to which they attach a `NullHandler`. This addresses the "no handlers could be found" problem. Their tests explicitly configure handlers, just like ours do. scrapy is more hands-on. It provides a configuration module for its logging and a whole document on how to handle logging with scrapy. It looks like log.py's whole reason for existence is making sure that a handler is attached to to the scrapy handler at startup. I think the extra complexity here is because scrapy also offers a CLI, so there has to be some way to configure logging without resorting to writing python, so I felt we didn't need to resort to this added complexity. --- Based on all of the libraries I've looked at, I think our current approach is reasonable. The one change I would make is to explicitly configure a `grpc` logger and to only attach a `NullHandler` to it instead of putting the burden on the author of each new module to configure it there. With this change, I have - Configured a logger in each module that cares about logging - Removed all NullHandlers attached to module-level loggers - Explicitly configured a `grpc` logger with a `NullHandler` attached Resolves: #16572 Related: #17064	6 years ago
Jan Tattermusch	5344c81f3c	switch C# to contextual serializer and deserializer internally	6 years ago
Muxi Yan	861e7ce452	nit fixes	6 years ago
Muxi Yan	37dbad80d5	Refactor channel pool	6 years ago
tongxuan.ltx	c21393e553	g_default_client_callbacks shouldn't be global variable In tensorflow, RPC client thread doesn't active release, rely on process to cleanup. If process have already cleanup the global variable(g_default_client_callbacks), after that client issue a RPC call which contains the ClientContext, then once ClientContext destructor called, pure virtual functions call error is reported.	6 years ago
Muxi Yan	d72d5b2c8e	Some nit fixes	6 years ago
Vijay Pai	926b2941ab	Pre-request 32 callbacks of each method	6 years ago
Vishal Powar	88352c827f	Address review comments	6 years ago
Jan Tattermusch	b187cfe460	regenerate protos	6 years ago
Jan Tattermusch	a50c61edc1	generate alternative BindService method	6 years ago
Jan Tattermusch	abbb317fee	add ServiceBinderBase	6 years ago
Arjun Roy	bc3d6d21b7	Set call_ member variable to null after freeing.	6 years ago
Arjun Roy	843c8d9e75	Fixed intermittent CPP sync server shutdown leak. Specifically: if a request handling thread is in flight but scheduled out when shutdown is called on the server, but it has already passed the shutdown check, then when it resumes it will add a grpc_call to the completion queue that is leaked. We fix this by explicitly freeing such calls after all worker threads have shutdown. To manifest the leak, run the end2end::ClientCancelsRequestStream test repeatedly on the unpatched server implementation. About 0.5% of the time, the leak will manifest.	6 years ago
Vishal Powar	0f24148733	Simplify the code in CreateRoundRobinPolicyArgsLocked() to always expect serverlist_ to be present.	6 years ago

... 5 6 7 8 9 ...

20117 Commits (1eb6b951e06643438b499e3093117246ff2b76a1)