fix: an asleep browser Lane is not a stalled one on the admin page #110
Reference in New Issue
Block a user
Delete Branch "fix/asleep-browser-lane-not-stalled"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
laneRow.StalledwasDue > 0 && Checked == 0, which is exactly the shape of the on-demand wake gate declining to start Chrome (ADR-0005): under five due Series and none overdue by 15m, a browser Lane reads nothing deliberately.kagane and novelfull each have exactly one bookmarked Series (kagane's other four
seriesrows are orphans, comix has none), so the 5-due count rule can never fire for them and the age rule is their only wake path — meaning "1 due / 0 checked" is their state for most of every cycle. The page marked bothnot checking, spending the one mark that means "go look" on the commonest healthy browser-Lane state.latest.LaneState.Asleepset at the wake gate (poller.go:266)Stalled, never contributes toAttentionbrowser asleepbeside the figuresTests:
TestBrowserLaneWakeThresholdsasserts the snapshot reportsAsleepwith 3 due / 0 checked and clears it on the waking pass;TestAsleepBrowserLaneIsNotMarkedStalledasserts the fragment says "browser asleep", not "not checking", and carries noattentionclass.go test ./...green.Behaviour verified in prod, not inferred: kagane and novelfull became due at 14:40Z and both polled at 14:55Z — rest +
browserWakeAge— novelfull picking up Chapter 4458.