-
Notifications
You must be signed in to change notification settings - Fork 1
feat(sql-fs): fence stale sandbox writers with durable epochs #161
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
Hazzng
wants to merge
5
commits into
main
Choose a base branch
from
voyage/c62365e4ef1c
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
5 commits
Select commit
Hold shift + click to select a range
c51189e
feat: add durable sandbox epoch migration
trek-ai[bot] bd8fb49
feat: fence postgres sandbox epochs
trek-ai[bot] b426171
feat(sql-fs): fence script scopes with sandbox epoch
trek-ai[bot] 9e24a7c
test: add postgres fencing regressions
trek-ai[bot] 5d3d3bd
fix: advance fencing epoch on composite writes
trek-ai[bot] 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
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.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
The test leaves a
sandbox_epochsrow behind, so a second run against the same database fails.Line 117 inserts
sandbox_epochswith the fixed keymigration-epoch-sandbox. The test deletes thesandboxesrow at line 120, but it never deletes the tombstone row.sandbox_epochs.sandbox_idis the primary key, so a repeated run of this test against a reused database raises a unique violation on the same INSERT.Delete the tombstone row after the final assertion. Keep the assertion order so the persistence check still runs before cleanup.
Tests that create a sandbox must delete it in cleanup, and integration tests should use
try/finallyfor cleanup. As per coding guidelines.🧹 Proposed cleanup after the persistence assertion
const tombstone = await afterRerun<{ epoch: string }[]>` SELECT epoch::text FROM sandbox_epochs WHERE sandbox_id = 'migration-epoch-sandbox' `; expect(tombstone).toEqual([{ epoch: "1" }]); + await afterRerun`DELETE FROM sandbox_epochs WHERE sandbox_id = 'migration-epoch-sandbox'`; } finally { await afterRerun.end({ timeout: 5 }); }Also applies to: 140-146
🤖 Prompt for AI Agents
Source: Coding guidelines