Timeout hit even though no timeout was specified
See original GitHub issueIn dsub 0.3.4, I just ran into an issue where I had a job running for a week that was terminated, saying Failure message: User specified operation timeout reached
.
However, I didn’t specify a --timeout
for this job. Looking at the docs and the user-facing code, I don’t see any place where a default timeout is set. Is there silently a default of 1 week if no --timeout
is set?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Build has Hit Timeout Limit - CircleCI Support
Timeout Limit CircleCI has a built-in 10 minute no-output timeout. This means that if it has been 10 minutes since the last output,...
Read more >Timeout for python requests.get entire response - Stack Overflow
If you want to timeout the request after 10 seconds, even if data is ... If no timeout is specified explicitly, requests do...
Read more >Taking a Timeout from Poor Performance | APIs You Won't Hate
Here's a plan: set the timeout to 400ms, add a retry after 50ms, then if the first attempt is taking a while boom,...
Read more >Azure App Service - prevent timeout after 230s - Microsoft Q&A
--Timeout will hit if the web application got the request and kept processing the request for > 4minutes without sending any data back....
Read more >Common Timeouts effecting Web Services, HTTP and SOAP ...
This timeout usually only occurs in situations where the writes are lagging behind new requests. This can occur when a client has a...
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 Free
Top 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
Hi @carbocation .
The default is indeed 7 days.
There is a command-line flag
--timeout
:The docs have been updated, closing out.