Level master with develop (CI green) - #2
Merged
Merged
Conversation
Schema seeding only ever needed a path, so a sibling checked out inside the workspace worked for it, while the cross-repo consensus guards resolve ../<repo> the way a developer checkout is laid out. Four of them failed on a run that had the sibling all along, just in the wrong place. The roster is now .ci-siblings, the same declaration the e2e venue reads, and both siblings are public, so the two read-only deploy keys are gone.
…rifies Two harness defects, both invisible until the e2e tier ran in CI for the first time, and both reproduced and fixed against a replayed schedule (PARITY_SEED=977000): 4 failing before, 4 passing after, and the whole tier 64 passing. The byte-identity oracle kept its own column-exclusion list and it had drifted from src/tableLifecycle.js, which already declares blocks.id as the local surrogate the applier strips on insert. Once a reorg renumbers the source the two sides are permanently offset there, by design, so the oracle failed on that column alone while every other column matched. It now derives the canonical half instead of restating it. The e2e TestDatabase was also missing doQueryStrict, which the integration harness has carried for a while with a comment explaining this exact failure. Without it the state-commitment conformance suite dies on "db.doQueryStrict is not a function", reporting a missing stand-in method as if the read were broken.
The armed-follower suite asserts that its temporary arming is restored, and pinned a set of one. BTC:testnet joined the contract-state slot at 146500, so the pin moves with the real map rather than describing a set that no longer exists.
|
|
…at genesis [XC-1355]
Both overrides sat one patch short of the fix: js-yaml 4.3.0 carries the quadratic !!omap CPU consumption advisory and brace-expansion 5.0.8 the unbounded-array DoS.
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
2 participants
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.
Brings master level with develop so the CI gate runs green on both branches.
This is a branch-levelling merge rather than a release train: no version bump,
no tag, no manifest. The next train cuts from develop as usual.
What is in it
The CI reds that were failing unnoticed until the public flip revived Actions,
each verified on a venue before landing:
xchain-vmis a gitignored path dependency thatnpm ciaccepts as missing;the job now stages it from the canonical sibling before installing
chain when the shadow window opened
fixtures seed blocks at fixed past timestamps and the tip-age freshness gate
correctly read the coin as frozen
DDL on three tables
guards, and its dispenser fiat-count pin was one behind the suite
Verification
Each fix was run on a venue with real databases before it was committed, and
the per-repo pre-push gate ran the full suite again at push time.