Allow resetting the request timeout with the same value
See original GitHub issueCurrently, when using ServiceRequestContext.setRequestTimeout
multiple times with the same value, the latter calls are ignored. It seems like there are use cases for refreshing the timeout multiple times per request, e.g. the timeout should be applied per message in a gRPC message stream. Currently, it’s actually still possible to do this with something silly like setRequestTimeout(timeout * numMessagesSoFar)
@trustin, does it make sense to remove the if
statement that guards against the same value in this function?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Resetting a setTimeout - javascript - Stack Overflow
in your click function, call clearTimeout window.clearTimeout(timeoutHandle); // then call setTimeout again to reset the timer timeoutHandle = window.
Read more >How to Increase Request Timeout in NGINX - Ubiq BI
By default, NGINX request timeout is 60 seconds. Sometimes you may need to increase request timeout in NGINX to serve long-running requests.
Read more >Setting request timeout (services) | Cloud Run Documentation
Click the Container tab. In the Request timeout field, enter the timeout value that you want to use in seconds. Use values ranging...
Read more >Setting and resetting the request timeout for a virus scan
Set a new scan request timeout value. value is a setting from 1 to 45 seconds. The recommended setting is between 8 and...
Read more >The Importance of Request Timeouts - DEV Community
Read timeouts cover the amount of time it takes to actually receive the response back from the server. Some HTTP clients allow you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d like to give it a shot.😄
Ah, I see. Yes, I made
setRequestTimeout
to update the timeout against the beginning of request. Not sure which is the ‘right’ behavior, though. Current behavior seems OK to me though.