A console tab left open across a deploy keeps running the old build, and nothing says so #181
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Seen with run 67 on 2026-10-16. Production deployed
74e261cat 21:30Z. At 22:45Z the user's console still drew a skip asstep.skipped: agent.judge.r2. That is the wording #175 replaced, and 74e261c's bundle has the new wording. The tab had loaded the old build before the deploy, and it kept running it.The tab is a single-page app with live streams. Nothing reloads it, and nothing tells the operator a new build is live. So after every deploy, the fixes it carries are invisible until a reload, and a bug report from that tab describes code that is no longer there (#179's third point was one).
Wanted
/api/statusalready carriescommit, and a new/healthzboot_idmarks a restart.Shipped in
bb5d87a(changeconsole-notices-a-deploy, commitbbb8686), live since 00:07Z on 2026-10-17, and archived in24bd393.committhat/api/statusnames. When osfd later names another, a quiet notice says "Braid was updated", with Reload and Not now.bb5d87astayed open across the deploy of35c556bat 00:34Z, and the notice appeared in its bottom right./api/statusitself and changes its commit under the page.Tabs opened before
bb5d87adon't have the notice yet. Reload those once by hand. Closing.step.skipp…#179