Repository navigation
Conversation
Fixes valkey-io#533. Previously, update functions in keys-browser.ts (e.g. updateStringKey, updateJsonKey, updateHashKey) performed read operations such as GET before issuing SET/SETEX without optimistic concurrency control, allowing write races if the key was updated concurrently. This commit wraps all update operations with client.watch([key]) and executes changes inside an atomic batch (Batch/ClusterBatch). If the watched key is modified concurrently, the transaction cleanly aborts and reports an optimistic lock conflict error. Signed-off-by: Raj Gahoi <gahoiraj01@gmail.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 3 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Signed-off-by: Raj Gahoi <gahoiraj01@gmail.com>
This branch has not been deployed
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.
Description
Fixes #533.
Previously, key modification functions in
apps/server/src/keys-browser.ts(e.g.updateStringKey,updateJsonKey,updateHashKey,updateListKey,updateSetKey, andupdateZSetKey) performed pre-write validation reads (such as checkingGETfor binary content) and non-transactional command sequences without optimistic concurrency control. If another client modified the key between the read and write operations, races and silent data overwrites could occur.This pull request implements optimistic locking via Valkey's
WATCHand atomic transactions (Batch/ClusterBatch):await client.watch([key])prior to reading or building updates for string, json, hash, list, set, and zset keys.client.exec(batch, true)).client.unwatch()if validation fails or an exception occurs.nulltransaction responses (aborted due to concurrent modification) and surfaces an informative error: 'Key was modified by another client during edit (optimistic lock conflict).'.Testing
apps/server/src/__tests__/keys-browser.test.tsto verify thatwatch, atomic batch execution, and un-watch on abort operate as expected.