Eight gates were green because nobody asked them - #2763
Merged
Conversation
…y ran
Dispatching all 27 unmeasured workflows at master, twelve refused. They are
registered with Actions, listed as active, and have no file in the tree:
13 of 59 active workflow(s) have NO FILE
.github/workflows/ci.yml (CI)
.github/workflows/coq-ci.yml (Coq Verification)
.github/workflows/test.yml (t27 CI)
...
Deleted from the repository, never deregistered. Calling them unmeasured is
wrong twice: they can never run, so they will never be measured, and they
inflate the count of gates someone might go and fix. `tri gates unmeasured`
reports them under their own heading now and excludes them from the total.
before: 28 of 58 unmeasured
after: 13 ghosts, and 1 of 46 unmeasured
The 1 is Issue Gate. The other 26 got a real reading from the dispatches --
which is the whole point of yesterday's `workflow_dispatch` change, used once.
Also: check_now_entry_shape.py went red on those dispatches, correctly and
uselessly. Its subject is a pull request; a dispatch is not one, so there is no
set of added entries to read. That is not the same as a run that should have had
one and did not, and it now says NOT APPLICABLE and exits 0, while a
pull_request event with no base SHA still exits 2. Found by the dispatch sweep,
which is what a dispatch is for.
Refs #2754
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ndencies
Both Build Agent Runner and Build & Push Sandbox Image build
contrib/backend/agent-runner, whose Dockerfile pinned rust:1.82-bookworm. A
dependency now requires edition 2024, which arrived in 1.85:
error: failed to parse manifest ... feature `edition2024` is required
Neither workflow had run since June -- both were in the 28 that
`tri gates unmeasured` named -- so the pin went stale with nobody watching.
Dispatching them is what surfaced it.
Moved to the floating `rust:1` tag, which bootstrap/Dockerfile and Dockerfile
already use and which cannot go stale the same way again.
Refs #2754
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Refs #2762 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-28 19:38:23 UTC
Summary
Seal Status
|
…-140) -o /dev/null is not a free discard: rustc writes metadata through a temp file beside the output, so the Rust column read 0 of 559 for its whole life. A column at exactly zero while its siblings are not is a claim about the instrument. Dispatch every gate once -- the readings are the payload. Twelve refused because their file is gone; eight ran and failed, none of them new; two failed correctly, which is worth checking before filing. And NOT APPLICABLE is a third answer a gate needs when its subject is absent. A gate catching its author is the gate working, and worth saying out loud. Refs #2762 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-28 19:39:00 UTC
Summary
Seal Status
|
Up to date for the ruleset after #2761.
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-28 19:50:34 UTC
Summary
Seal Status
|
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.
Refs #2762
tri gates unmeasurednamed 28 workflows with no default-branch run in 30 days. All 27 that could be were dispatched atmaster. This is what came back.Twelve refused: they have no file
13 of 59 workflows GitHub lists as active have no file in the tree — deleted from the repository, never deregistered. They can never run, so they can never be measured, and they inflate the count of gates someone might go and fix.
tri gates unmeasuredreports them under their own heading now and excludes them from the total:The 1 is
Issue Gate. The other 26 got a real reading — which is what theworkflow_dispatchadded in #2759 was for, used once.Eight ran and failed
Every one had been true and invisible since June. The full table is in #2762; one cause is fixed here:
Build Agent RunnerandBuild & Push Sandbox Imageboth buildcontrib/backend/agent-runner, whose Dockerfile pinnedrust:1.82while a dependency now needs edition 2024 — which arrived in 1.85. Moved to the floatingrust:1tag thatbootstrap/Dockerfilealready uses.The most interesting of the rest: Brain Seal Refresh fails with
GH013: Repository rule violations found for refs/heads/master. It exists to push refreshed seals tomaster, and the branch ruleset forbids exactly that. It cannot succeed as written.Two red dispatches were correct
check_now_entry_shape.pyreads thedocs/now/entry a pull request adds. A dispatch has no pull request, so failing there was failing at something outside its subject. It now says NOT APPLICABLE and exits 0, while apull_requestevent with no base SHA still exits 2.tri: 208 tests passing.🤖 Generated with Claude Code