Ensure redis mutex is always released even context cancelled#5721
Merged
Conversation
Use context.WithoutCancel in the deferred unlock so the lock is always released even when the request context is cancelled (e.g. client disconnect). Introduce Handle.WithMutex to centralise the lock/unlock pattern and avoid repeating the fix at every call site.
tung2744
changed the title
carmenlau
approved these changes
May 14, 2026
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
2 participants
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.
Use context.WithoutCancel in the deferred unlock so the lock is always released even when the request context is cancelled (e.g. client disconnect). Introduce Handle.WithMutex to centralise the lock/unlock pattern and avoid repeating the fix at every call site.
ref DEV-2587