Repository navigation
feat(hql2): recover truthful typed ANALYZE diagnostics - #247
Merged
Merged
Conversation
Freshair129
marked this pull request as ready for review
October 19, 2026 05:13
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.
Summary
Recover the approved G4 diagnostic implementation left on the archived HQL2 branch (
ed75e16d, strengthened byd385c608) onto current main5eb2fa4.Validation
--locked --no-default-features --features bins --jobs 2 --libplus the named targets above; no unfiltered stress/probe/soak suite was run locally.-D warningsand no lint suppression.--no-default-features --features bins --bin genesis-db-server): passed.cargo fmt --checkandgit diff --check: passed.c824971db49f385f48d4d8afff247a349008d965must finish green before merge.Compatibility and qualification
C-3 / HIGH. Core v2 diagnostic consumers must migrate from the preliminary fields to the approved typed readings. Request/envelope versions, planner identity, normal rows, persistence and v1 behavior are unchanged. No new transport route or user-database migration is introduced.
The scoped architecture review is by the implementer, not an independent review. This closes the bounded archived-code recovery only; broader G4/P8/P13, independent, device and release qualification remain open. Merge requires completed local validation and green hosted checks at the exact PR head.
Hosted incident and fixture follow-up
The first Windows job failed three annotation ACL cases in the shared database-ID setup helper with
QUERY_BUDGET_EXCEEDED / query_limit. The budget dimension and underlying runner cause remain unconfirmed; a similar historical Windows budget incident exists in the P8 report.The helper used a complete timed Values query solely to obtain fixture metadata. It now derives the expected database ID from the existing P8 public-key fingerprint contract. All annotation assertions are preserved. This follow-up changes one test helper and adds its RCA; production query budgets and engine code are unchanged. The initial failure is retained as evidence, and merge waits for fresh hosted checks at the updated head.
Final hosted qualification and merge
At head
c824971db49f385f48d4d8afff247a349008d965, 49 checks succeeded and 5 conditional checks skipped; all 10 workflows completed successfully, including Tests and Mobile Build. The full Windows suite passes, including all three initially failing annotation cases. Merged normally with ancestry preserved as7472079d37a91a81a85fc0a57824156a13481e71.