hazync board: show the block the frontier is waiting on - #897
Closed
defenwycke wants to merge 1 commit into
Closed
defenwycke wants to merge 1 commit into
defenwycke wants to merge 1 commit into
Conversation
The coordinator has published `blocked` in /api/state since hazync#284: the block the chained frontier needs next, its status, how long the frontier has waited, and whether that needs a human. Nothing on the board read it, so a frontier held for hours looked identical to a healthy one. On 2026-09-13 block 55,862 (3,261 segments) held the frontier for ~2h43m while every pipeline bar kept moving; the only place that said so was the raw JSON. Adds a Frontier card between the metric tiles and the pipeline: block number, a proving/open/needs-attention pill, the claim holder and claim age (from `claims`), how long the frontier has waited, and the coordinator's own explanation. Server text is written with textContent only. The card stays hidden when `blocked` is absent (older coordinator, or no live data).
Contributor
Author
|
Closing: not what was wanted. The ask is a coordinator log view showing all of the coordinator's outputs, not a single frontier card. |
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.
What
A Frontier card on the Hazync board (
ghost-web/hazync.html), between the metric tiles and the pipeline. It shows:blocked.block)proving,open, orneeds attention(blocked.needs_attention, in a new warning colour)claims)blocked.stalled_for)blocked.why)Why
The coordinator has published
blockedin/api/statesince hazync#284, but nothing on the board read it. A frontier held for hours looked identical to a healthy one.On 2026-09-13, block 55,862 (3,261 segments) held the frontier for about 2h 43m while every pipeline bar kept moving. The only place that showed it was the raw JSON.
Notes
textContentonly.blockedis absent (an older coordinator, or the unavailable-data fallback), so nothing changes for a coordinator that predates backup: manual export/verify/import handlers are stubs (UI fakes success) #284.?slim=1already carriesblockedandclaims(checked against the live API), so no extra request is needed.whytext is the coordinator's wording. Past two claim cycles it says the holder "may be failing on a bug already fixed". For 55,862 that was wrong: the block was simply huge. Once this ships, that sentence appears publicly. Adjusting it belongs in the coordinator (hazync#285 coversstalled_forcrying wolf on large blocks), not here.Tested
Rendered in headless Chromium through a local proxy of the live coordinator:
block 59,626 · proving · held by ghost:dda215)needs_attentionpayload, injectedNot deployed. The live page matched
mainbyte for byte (77d43acb9872) before this change.