-
Notifications
You must be signed in to change notification settings - Fork 113
Persist UI4T canvas layout and harden canvas locking #1452
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
pratzrao
wants to merge
4
commits into
main
Choose a base branch
from
enhancements/persistent-canvas-layout
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.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a255cb3
feat(transform): persist canvas layout and harden locking
pratzrao 0176387
fix(transform): address static analysis findings
pratzrao 18a369b
fix(tests): annotate fixture registration imports
pratzrao 2542067
Merge remote-tracking branch 'origin/main' into enhancements/persiste…
pratzrao 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
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
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.
🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🌐 Web query:
For Django 4.2, confirm when a row lock acquired with QuerySet.select_for_update() is released relative to transaction.atomic() scope.💡 Result:
In Django 4.2, a row lock acquired with QuerySet.select_for_update is held until the end of the transaction in which it was acquired [1][2]. Because select_for_update must be executed within a transaction, it is typically used inside a transaction.atomic block [2][3]. The lock is released exactly when the transaction concludes (i.e., when the transaction.atomic block exits) [1][2]. If the block finishes successfully, the transaction is committed, and the locks are released as part of that commit process [4][5]. If an exception occurs within the block, the transaction is rolled back, and the locks are similarly released [4][5].
Citations:
🏁 Script executed:
Repository: DalgoT4D/DDP_backend
Length of output: 45612
🏁 Script executed:
Repository: DalgoT4D/DDP_backend
Length of output: 50376
🏁 Script executed:
Repository: DalgoT4D/DDP_backend
Length of output: 736
🏁 Script executed:
Repository: DalgoT4D/DDP_backend
Length of output: 31461
Retain the workspace lock for each complete mutation.
validate_canvas_lockreleases theOrgDbtrow lock when its inner transaction exits. Most callers then modify database records or dbt project files outside that transaction. A concurrent request can therefore proceed, and another user can acquire the expired lock while the first mutation continues.Wrap each mutation in an outer
transaction.atomic()so the lock remains held through the mutation. Useput_canvas_layoutas the pattern. Add tests for concurrent mutations and lease expiry during a mutation.🤖 Prompt for AI Agents