Add regression test for stale cached-null + duplicate-key race condition in GrouperWorker#537
Closed
Add regression test for stale cached-null + duplicate-key race condition in GrouperWorker#537
Conversation
Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com>
Contributor
Author
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
[WIP] Update event cache invalidation for duplicate key error
Add regression test for stale cached-null + duplicate-key race condition in GrouperWorker
Mar 6, 2026
|
Thanks for adding a description — the PR is now marked as Ready for Review. |
2 similar comments
|
Thanks for adding a description — the PR is now marked as Ready for Review. |
|
Thanks for adding a description — the PR is now marked as Ready for Review. |
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.
The existing
CacheControllermock always invokes the resolver and treatsdelas a no-op, making it impossible to reproduce the race condition where a stalenullis cached and must be invalidated before a retry. Without a real caching layer in tests, the infinite-recursion bug introduced by a duplicate-key error could silently regress.Changes
CacheController— usesjest.requireActualto bypass the global mock, giving the test genuine cache semantics (null is cached;delactually evicts)null(Worker A's stale entry); the unique index ongroupHashcauses the realinsertOneto throw E11000cache.delwas called with the exact stale key, and thattotalCountincrements to 2 (retry found the DB record and processed it as a repetition rather than recursing)✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.