🤖 fix: provider settings subscription race condition #1066
Merged
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.
The
onConfigChangedsubscription handler was dropping notifications when no listener was actively waiting for them. This caused provider settings updates to not propagate reliably until window reload.Root Cause
The async generator pattern in the subscription was:
Bug: If the callback fired before step 2 (before entering wait state), the notification was silently dropped because
resolveNextwas null.Fix
Added a
pendingNotificationflag that queues notifications arriving before the listener enters its waiting state. When the iterator loops, it checks this flag first and yields immediately if a notification is pending.Generated with
mux