Repository navigation
Fix the booting FIRST-PAINT watch race (event-driven paint) - #281
Merged
Merged
Conversation
The paint was a single shot at wall-clock +600 ms behind seed's +500 ms sleep: a 100 ms margin the throttled CI container ate (shard 2/2, 2026-09-30) - a stretched seed sleep started the watch after the paint, and a late capture child never saw the byte again. The pane now waits on a go-file (nothing can paint before the watch is armed, so `before` is still genuinely blank) and repaints every 150 ms, comfortably inside the 200 ms no-growth budget and above the 60 ms quiet beat, so the watch still ends on the FIRST paint going quiet - the claim the case pins.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The pane-repaint
bootingcase armed its single-shot paint at wall-clock +600 ms against seed's +500 ms sleep - a 100 ms margin CI's throttled container ate (shard 2/2 red on #280, which touches nothing here). The pane now waits on a go-file and repaints every 150 ms: nothing can paint before the watch is armed, the first paint always lands inside the 200 ms budget, and the 60 ms quiet beat still ends the watch on the FIRST paint. 9/9 x4 locally.