Skip to content

test(extensions): cross-process concurrency stress for W2 lifecycle services (swamp-club#254) #1320

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.

Sign up for GitHub

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
stack72 merged 3 commits into from
May 5, 2026
Merged

test(extensions): cross-process concurrency stress for W2 lifecycle services (swamp-club#254) #1320

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
48951df
test(extensions): cross-process concurrency stress for W2 lifecycle s…
stack72 May 5, 2026
f84dcf6
test(extensions): normalise path separators in invariant (iv) for Win…
stack72 May 5, 2026
866b3b4
test(extensions): tolerate W2 SQLite-contention recovery transient
stack72 May 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions design/extension.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1007,6 +1007,17 @@ For rm, the catalog tombstone is the **first** mutation, so a fault
inside that `saveAll` leaves all three layers (catalog, lockfile, FS)
in their pre-rm state — a retry is a clean re-rm.

The cross-process composition of these per-extension atomicity claims —
that `saveAll`'s SQLite WAL transaction, the lockfile advisory-lock retry,
and the asymmetric ordering above all hold under concurrent invocation
from independent OS processes against the same repository — is verified
by `integration/lifecycle_concurrent_stress_test.ts` (swamp-club#254). The
test runs 50 iterations of four concurrent `swamp` subprocesses each
(`extension pull` × 2 distinct extensions, `extension rm`, `extension
update`) and asserts catalog↔lockfile↔FS bijection, well-formed lockfile
JSON, no `DuplicateTypeError` leakage across distinct fixture types, and
no lockfile-retry-budget or SQLite-busy exhaustion at iteration end.

### W3+ inheritance

The lifecycle services' shape is W3-stable. The unified loader
Expand Down
Loading
Loading