fix(proxies): share the refusal store across duplicated server module copies - #15316
Open
maxmad64bis wants to merge 1 commit into
Open
maxmad64bis wants to merge 1 commit into
maxmad64bis wants to merge 1 commit into
Conversation
maxmad64bis
force-pushed
the
fix/refusal-store-shared-state
branch
2 times, most recently
from
October 2, 2026 08:55
5ad3678 to
024f1de
Compare
maxmad64bis
marked this pull request as ready for review
October 2, 2026 09:02
maxmad64bis
force-pushed
the
fix/refusal-store-shared-state
branch
from
October 2, 2026 15:08
024f1de to
d48968a
Compare
This was referenced Oct 2, 2026
Open
maxmad64bis
force-pushed
the
fix/refusal-store-shared-state
branch
from
October 4, 2026 12:37
d48968a to
285b96b
Compare
This branch has not been deployed
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.
Summary
The server bundle can hold several copies of the refusal store, one per module graph, so failures recorded by the patched global fetch never reached the account rotation that reads the store: repeated connection resets through one egress kept serving it. The store and its listener list now live in one process-wide object, the pattern already used for the fetch capture context.
Related Issues
Validation
npm run lintTests Added Or Updated
tests/unit/proxy-refusal-memory-single-instance.test.ts(new, 4 cases: distinct modules witness, cross-copy set-aside visibility, cross-copy transport evidence, cross-copy slow evidence)tests/unit/proxy-transition-bridge-single-emit.test.ts(new, 1 case: two bridge copies, oneproxy.set_asideemission)Coverage Notes
open-sse/utils/proxyRefusalMemory.ts: covered by the single-instance tests (cross-copy reads after writes through another copy)open-sse/utils/proxyTransitionListeners.ts: covered by both new test files (shared listener set, idempotent keyed subscription)src/lib/proxyEvents/proxyTransitionBridge.ts: covered by the single-emit test (stable subscription key)Reviewer Notes