Skip to content

test(spec): the transactions tombstone pin discriminates its own subject #19078

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
os-bill merged 1 commit into from
Sep 18, 2026
+9 −2
Merged

test(spec): the transactions tombstone pin discriminates its own subject #19078

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 9 additions & 2 deletions packages/spec/src/data/driver.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,9 +121,16 @@ describe('[#4634] the 31 inert capability bits are tombstoned, not stripped', ()
);
});

it('the transactions prescription points at method presence, and says the live bit is not it restored', () => {
it('the transactions prescription points at the DECLARATION gate, not method presence alone, and says the live bit is not it restored', () => {
// [#18996] Anchored on what #18890 made load-bearing: the NEGATION and the
// predicate that replaced method presence. An anchor on `METHOD PRESENCE`
// alone matched this prescription's PREVIOUS, now-false opening ('gated on
// METHOD PRESENCE — `driver.beginTransaction`') exactly as happily as the
// true one, so it could not fail on the one shape it exists to catch. ⛔ Not
// a ban on the phrase — `schemaSync`'s own 'gated on METHOD PRESENCE'
// sentence is true of the runtime and stays.
expect(() => DriverCapabilitiesSchema.parse({ transactions: true })).toThrow(
/DriverCapabilities\.transactions.*removed.*METHOD PRESENCE.*beginTransaction.*Delete the key/s,
/DriverCapabilities\.transactions.*removed.*no longer on METHOD PRESENCE.*driverSupportsTransactions.*beginTransaction.*Delete the key/s,
);
// [#18063] The trap this sentence exists to close: a reader who sees a live
// `transactionsUnsupported` and concludes the retired key came back. It did
Expand Down
Loading