-
Notifications
You must be signed in to change notification settings - Fork 1
fix(session): destroy reaches warm replicas via tombstone + sandbox-gone guard (F7) #155
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| --- | ||
| "sql-fs-api": minor | ||
| --- | ||
|
|
||
| fix(session): destroy now reaches warm sessions on other replicas (F7). | ||
|
|
||
| Destroying a sandbox on one replica previously left warm sessions on other | ||
| replicas serving ghost state: a written session would reload a deleted tree | ||
| into an empty pathCache (surfacing as a non-zero exit + garbage stderr inside an | ||
| HTTP 200 exec), and a never-written session would never reload at all because | ||
| the deleted version key read as 0 and matched its `lastSeenVersion === 0`. | ||
|
|
||
| Two layered fixes: | ||
|
|
||
| - Primary (Redis-independent): `SqlFs.reload()` now detects a zero-row | ||
| `loadAllPaths` — which for a live sandbox always returns at least its root dir | ||
| — and throws a typed `ESANDBOXGONE` instead of installing an empty pathCache. | ||
| The session manager catches it, tears the stale warm session down (drops it | ||
| from the pool and disconnects the per-session Postgres pool), and surfaces a | ||
| clean `ENOENT` → 404. | ||
| - Secondary (tombstone): `destroy` now writes a distinct `DESTROYED` sentinel to | ||
| the version key (with the version-key TTL) instead of deleting it. | ||
| `ensureFreshCache` recognises the sentinel before the numeric parse and tears | ||
| the session down — covering the never-written variant. Re-creating a | ||
| tombstoned sandbox clears the sentinel and starts cleanly at version 0. |
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.
Uh oh!
There was an error while loading. Please reload this page.