-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP Support configurable client deadlines #30
Open
Shehab7osny
wants to merge
132
commits into
nfultz:master
Choose a base branch
from
Shehab7osny:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This argument will be used to manually configure the deadline for client timeout. It will be helpful for those RPCs that take longer than 5 seconds.
This is done automatically after compiling the project. However the only difference will be the edited arguments only.
This argument is measured in seconds, and then multiplied by 1000 to convert it to microseconds to pass it to the gpr_time_from_millis() function
This is done automatically after compiling the project. However, these are the main differences in this file after compiling the project.
Shehab7osny
changed the title
These are the changes required to solve the issue #28 (Support configurable client deadlines in call())
Support configurable client deadlines
Apr 20, 2020
nfultz
changed the title
Support configurable client deadlines
WIP Support configurable client deadlines
Apr 20, 2020
nfultz
reviewed
Apr 20, 2020
This will add client_deadline argument to the options() for client timeout options.
Here I removed the argument passed to the grpc_client function in order to avoid breaking the existing code. The argument will be set in options()
the options() function will set the parameter client_deadline for 10 seconds to test the timeout issues. I tested the code on this example and setting the client_deadline for 0 seconds will raise the exception '"gRPC c++ call timeout". While testing for any seconds greater than 0 worked perfectly!
After running the roxygen, Namespace was not altered and the Description file just updated the RoxygenNote to 7.1.0
Added the server-side streaming functionality in the server-side R code
Overall this is looking pretty good. A couple minor points on organization
Other todo's:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I did the following updates to solve the issue related to client-side deadline. I hope that these updates solve the problem. I tried my updated code on the example (Helloserver and Helloclient) and it worked perfectly. I think it will work on any other example too.