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.
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
feat(termination)!: make container termination timeout configurable #2926
feat(termination)!: make container termination timeout configurable #2926
Changes from 10 commits
8632a79
ac8ce58
4cdb318
d994d55
c38f36b
1377520
6f16fa0
6461173
ac27a52
f4c786f
12a8722
f6d6fd2
4ccbbb1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I wonder why we need a separate parameter for the timeout when a context is already provided to
Terminate()
?As a user, I expect this to work fine. Does this code not do what is expected?
If a
Duration
value is needed (vs reacting to a channel close),ctx.Deadline()
returns a deadlineTime
. It seems that there is no need for a new API.