disconnected clients: TaskGroup validation
#12418
Merged
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
…disconnect are mutually exclusive.
…after_client_disconnect cannot both be set
DerekStrickland
added a commit
that referenced
this pull request
Apr 5, 2022
* TaskGroup: Validate that max_client_disconnect and stop_after_client_disconnect are mutually exclusive.
DerekStrickland
added a commit
that referenced
this pull request
Apr 6, 2022
* TaskGroup: Validate that max_client_disconnect and stop_after_client_disconnect are mutually exclusive.
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Added validation logic that both
max_client_disconnectandstop_after_client_disconnectcannot be configured at the same time for the same task group.