Ragnor Comerford ebf5a5769d tests: pin UPDATE RYW under in-process concurrency (red) ... Per AGENTS.md rule 8, this commit lands the failing regression test ahead of the fix so the red → green pair is visible in git log. The test asserts the RYW invariant for in-process concurrent UPDATEs on the same row: exactly one writer commits and N-1 receive 409 manifest_conflict. Currently fails on f925ad1 with 1 x 200 + 7 x 500: > "storage: Retryable commit conflict for version 6: This Update > transaction was preempted by concurrent transaction Update at > version 6. Please retry." Lance's transaction conflict resolver correctly detects the Update vs Update race, but the error wraps as `OmniError::Lance(<string>)` and the API surfaces it as 500 internal rather than 409 retryable conflict. Users see "internal server error" for what is documented as a retryable conflict path. The fix lands in the next commit: an op-kind-aware drift check at the commit_all entry that returns 409 ExpectedVersionMismatch for tables whose first touch was Update / Delete / SchemaRewrite when the staged dataset version drifts from the manifest pin under the queue. Closes the bug class "Lance internal conflict surfaces as 500 instead of 409" rather than mapping the specific Lance error variant — the right architectural layer (engine boundary, under the queue) catches the drift before commit_staged ever runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-08 16:33:53 +02:00
..
omnigraph	tests: failpoints schema_source().as_str() (CI fix)	2026-05-08 16:26:23 +02:00
omnigraph-cli	mr-686: bundle PR 0/1a/1b foundation + PR 2 catalog/schema_source ArcSwap	2026-05-07 16:22:38 +02:00
omnigraph-compiler	release: bump version to 0.4.1	2026-05-02 23:20:50 +02:00
omnigraph-server	tests: pin UPDATE RYW under in-process concurrency (red)	2026-05-08 16:33:53 +02:00