Cap execution timeout at 5 minutes #509
Open
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
coditva
force-pushed
the
feature/cap-execution-timeout
branch
from
c74b3b8
to
e8238f1
Compare
coditva
force-pushed
the
feature/cap-execution-timeout
branch
from
e8238f1
to
cdaadd6
Compare
|
Are we sure we want to set max to 5 minutes. The defaults on other places are 3 minutes of I’m recalling right. Can we cross check once in runtime? |
|
Also this seems to be a bit off here in how we are implementing hard limits. The hard limit is a separate option that, if optionally set, prevents any option or collection level user options from crossing it. |
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.
No description provided.