docs(e2e): record REG-09 as fixed at source, pending a platform release - #481
Merged
Conversation
PPT-2642 is root-caused and fixed in pg-orm 2.2.4, picked up by staff-api in #386. The row now says what was actually wrong, what the measurement was, and the one caveat that matters for reading a nightly result: e2e/stack pulls placeos/staff-api:latest, which is a release image, so this suite keeps running the old behaviour until the next platform release. Harmless in practice, because nothing in the suite bursts concurrent bookings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Docs only. PPT-2642 is root-caused and fixed — pg-orm#19 released as v2.2.4, picked up by staff-api in PlaceOS/staff-api#386.
The row now records what was actually wrong (crystal-db clears a connection's transaction flag only after the COMMIT it issues, so a failed COMMIT leaves it set and the connection goes back to the pool mid-transaction), the measurement (control stranded a connection in 3 of 4 bursts and ended unable to write; fixed, 0 of 11 and still writable), and the one caveat that matters when reading a nightly result:
e2e/stackpullsplaceos/staff-api:latest, which is a release image — so this suite keeps running the pre-fix behaviour until the next platform release rebuilds it. Harmless in practice, since nothing in the suite bursts concurrent bookings, but worth knowing before someone reads a green nightly as proof the fix is in.🤖 Generated with Claude Code