fix(effect): tolerate repeated reactivity keys during query cleanup - #7742
Merged
tim-smart merged 3 commits intoSep 3, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: bba6d89 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|
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.
Type
Description
Reactivity.querycleanup could throw when a key or record ID was repeated. The first occurrence removed the last handler and its map entry, then the next occurrence tried to use the missing set.Cleanup now skips keys that are no longer registered. The regression test uses the public query API and lives in the existing
Atom.test.tssuite.Verification
pnpm test --run packages/effect/test/reactivity/Atom.test.tspnpm lint-fixpnpm checkRelated
Closes #7741
Closes EFF-1087