Repository navigation
Conversation
A rebuild with the case builder settles ten cases whose receipts landed without a rebuild: six observed cases take the expect their receipts agree on (three reject, three accept with a semantic stage), and four accepted cases gain the semantic stage their receipts record. No case is added or removed and no SQL, setup or session changes.
This was referenced Nov 7, 2026
Contributor
Author
|
Closing: SQLQuack lands through local-gate trains, not PR merges (D94), so open PRs only add clutter (D628/D630). The branch is kept. Any work here that isn't on main yet is tracked by the train owner and lands through a train. |
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
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.
Rebuilding the cases settles ten cases whose receipts are already on main. No case is added or removed, and no SQL, setup or session changes. This PR lands those settlements so that main's case files match what the builder produces.
Generated with
python -m scripts.build_syntax_cases ddl dml query utility expressions --receipts coverage/syntax/receipts --held coverage/syntax/held.jsonland #142's setup-lookup fix applied. Main's builder can't regenerate these files on its own: it falls back to the wrong run-database setup for about 60create-warehousecases and 13 IPADDRESS/UUID cases, which also makes some of these settlements miss. This PR doesn't include that fix; it should land after #142. The other five families rebuild unchanged.The marks files gain the matching six "settled" rows. The stage is informational and is never scored.
syntax-coverage diff coverage/syntax/baseline.json:awaiting_observationtodisagreement. Snowflake rejectsCOPY INTO 'azure://…' FROM v1 = ( ) ;as a syntax error, but the parser accepts it. That's a parser gap, now visible, not a regression.Draft: waiting on the audit and a slot after #142.