fix: Notification to waiting clients during drop#201
Open
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #201 +/- ##
==========================================
- Coverage 74.95% 74.90% -0.05%
==========================================
Files 6 6
Lines 519 518 -1
==========================================
- Hits 389 388 -1
Misses 130 130 ☔ View full report in Codecov by Sentry. |
Owner
|
Sorry, I still don't completely understand why this is necessary. Why doesn't my call stack in #194 (comment) hold? If something is returning an empty approval iter in a state where that is not sufficient, why is that? Pointing at an existing test case doesn't help me because that test already passes today. |
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.
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_backkeeping 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::puttopool.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