Repository navigation
Correct drainPendingOpeners javadoc and document SETTINGS-raise test scope - #2295
Merged
Merged
Conversation
This file contains hidden or 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
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.
Motivation:
The offerPendingOpener javadoc claims drainPendingOpeners "only re-offers" a queued opener on a draining connection, which it never does, and the SETTINGS-raise test does not record what it pins.
Modification:
Reword the javadoc: the opener stays queued because tryAcquireStream refuses once draining/closed.
Comment raisedLimitDrainsMultiplePendingOpenersInOrder with its scope and the sibling test for slot accounting.
Result:
Comments only, no behaviour change.