Repository navigation
chore: get CI past scalafmt, so the job reaches compile and test again - #33
Merged
Merged
Conversation
Not part of this branch's change, and not a new break: `scalafmtCheck` has been failing on main since at least 2026-08-19 over this file, so every CI run — main's own included — has been red before reaching compile or test. Two docstrings were rewrapped by hand and the formatter was not re-run; this is its output, five lines of comment reflow with no code touched.
heimdall has no `demo` subcommand any more — `run-spo` is the epoch loop, and it is what three local instances converge on over HTTP. The docstring named a command that no longer exists, which is the one thing a reader would try.
The `it` project's federation scaffolding landed unformatted on 2026-08-13 and `scalafmtCheckAll` covers it, so every CI run since — main's own included — has failed before reaching compile or test. Eight files, all line wrapping: no expression changed, only where it breaks.
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.
CI has failed on
maincontinuously since at least 2026-08-11, and it fails at the first step of;scalafmtCheckAll;compileAll;testOnly binocular.*— so nothing has compiled or been tested in CI for ten days. This clears the formatting so the job reaches the parts that matter.Three commits, no behaviour changed:
DeployBridgeCommand.scala— two docstrings rewrapped by hand without re-running the formatter. Five lines of comment reflow.demosubcommand is gone —HeimdallCli.scala's docstring pointed atheimdall demo, which no longer exists; the epoch loop isrun-spo, and that is what three local instances converge on. One word, and the one thing a reader would have tried.itproject — its federation scaffolding landed unformatted with438d8e0on 2026-08-13, which is where the current red streak begins.scalafmtCheckAllcoversit, so those eight files have blocked every run since. Pure line wrapping: no expression changed, only where it breaks.sbt scalafmtCheckAllpasses locally, and in CI: 101 + 62 + 13 + 1 sources checked clean.The one test that still fails is meant to
With the formatting out of the way the CI command runs to the end. 584 of 585 tests pass; the failure is
BinocularBlueprintTest's drift guard onBitcoinContract, and it is deliberate.6dafbf8(2026-08-18) pinned the oracle blueprint BACK to the bytes the chain actually holds, because the Scalus upgrade at6d1e2abmoved the compiled hash and the live preprod oracle was minted before it — main derivese6fd5d76where the chain holds83d66490. That hash parameterizespeg_inand the TM validator, so building against a forward pin yields a bridge bound to an oracle with no UTxO, invisible untilconfirm-tmtxstops confirming. In that commit's own words: it goes green again by redeploying the oracle, not by re-pinning forward.So do NOT run
blueprintPinto clear this. Nothing here touches it.What this PR changes is that the guard is now reached. Since 2026-08-13 the job died at
scalafmtCheck, so no compile ran, no test ran, and the one intentional red marker was indistinguishable from the eight accidental ones. After this, binocular's red light means the oracle is pending redeployment and nothing else.Related
#32 (deploy-script-refs publishes the treasury-movement validator) inherits this red CI. Once this merges, #32 gets rebased and its own copy of commit 1 drops out.