fix: Notification to waiting clients during drop #201
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.
Following up with @djc's intuition (re: #194) -- I noticed that the final call to
spawn_replenishing_approvals(approvals)
is incomplete due to empty approvals and returns early after several attempts toput_back
keeping 5 connections waiting. Due to this, the call stack doesn't reachpool.notify.notify_one()
at the end, and thepool.notify.notify_one()
invocation at every connection polling (i.e.) also fails.However, instead of adding
pool.notify.notify_waiters()
input_back()
which makes it redundant, replacingpool.notify.notify_one()
inPoolInternals::put
topool.notify.notify_waiters()
(no permit is stored to be used by the next call tonotified().await
) solves this. I tested with the same test case (shown below and already included in the main branch) provided by @xortive