-
Notifications
You must be signed in to change notification settings - Fork 666
fix(api): carry the full project id in cache and lock keys #6284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
WhoamiI00
wants to merge
5
commits into
Agenta-AI:main
Choose a base branch
from
WhoamiI00:fix/full-project-id-cache-keys
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+632
−37
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
0cd64e1
fix(api): carry the full project id in cache and lock keys
WhoamiI00 e9776e2
docs(pr): add before/after image for the cache key scope change
WhoamiI00 0a81d42
fix(api): fail lock renewal when the legacy key is gone
WhoamiI00 6b42d56
fix(api): release the legacy key when primary acquisition fails
WhoamiI00 2178a0b
fix(api): mark the legacy-key obligation before awaiting the claim
WhoamiI00 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🤖 get_repo_knowledge executed:
get_repo_knowledge Agenta-AI/agenta /tmp/coderabbit-repo-knowledge/agenta-ai-agenta-4b53879a/conventions /tmp/coderabbit-repo-knowledge/agenta-ai-agenta-4b53879a/learningsLength of output: 14349
🏁 Script executed:
Repository: Agenta-AI/agenta
Length of output: 17434
🏁 Script executed:
Repository: Agenta-AI/agenta
Length of output: 4012
Track cleanup for the primary claim.
If cancellation occurs after Redis writes
lock_keybut before_lock_engine.set()returns,finallyreleases onlylegacy_key. The primary lock remains until its TTL expires, so new callers can receive a blocked result while no caller owns the critical section.Set a primary cleanup obligation before the primary
SET. Clear it after a confirmed refusal or successful ownership transfer. Releaselock_keywith_release_if_ownerinfinally, using the existing best-effort cleanup pattern. Add a regression test that suspends after writinglock_key, then cancels the task.