Skip to content

[Capability] Suppress list-changed events during the initial registry load - #35

Closed
chr-hertel wants to merge 3 commits into
mainfrom
fix/issue-26-registry-listchanged
Closed

chr-hertel wants to merge 3 commits into
mainfrom
fix/issue-26-registry-listchanged

Conversation

@chr-hertel

Copy link
Copy Markdown
Owner

Registry dispatched a list-changed event per element while the deferred loader ran, publishing spurious frames onto a configured notification bus before any client had observed a list. Registrations are now routed through a helper that skips dispatch while loading is set — the load establishes the initial state before the first read returns, so no change is observable and no end-of-load event is needed.

Closes #26

Confidence: 9/10 — minimal guarded dispatch using the existing loading flag, covered by suppression and runtime-dispatch regression tests; full unit suite, cs-fixer, and phpstan pass.

@chr-hertel

Copy link
Copy Markdown
Owner Author

Merged upstream with modelcontextprotocol#480

@chr-hertel chr-hertel closed this Aug 24, 2026
@chr-hertel
chr-hertel deleted the fix/issue-26-registry-listchanged branch August 24, 2026 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[C3] Registry list-changed events fire during the initial load

1 participant