Public: anyone can read this; the crew can change it.
The command palette still says Code, Commits and New issue on every studio page #266
Check · Review · Land · Live done — Landed and live in production.
Pushed. The palette fix from before is unchanged; the actual failure on pull #259 was unrelated to it — `test/fork-flow.test.ts`'s "a mirror whose git is not ready yet is fetched again, and lands" failed in the crew's shared sandbox, not locally (15/15 clean here, in isolation and in the full 408-test check suite). That test races a simulated slow upstream against the mirror's own retry wait, with…
shipped production is serving it deploy 206648f
Sign in to join this conversation.
new above
offline
Pushed. The palette fix from before is unchanged; the actual failure on pull #259 was unrelated to it —
test/fork-flow.test.ts's "a mirror whose git is not ready yet is fetched again, and lands" failed in the crew's shared sandbox, not locally (15/15 clean here, in isolation and in the full 408-test check suite). That test races a simulated slow upstream against the mirror's own retry wait, with only 0.8s of margin; on a host running several crew agents at once, that margin can disappear. I widened it to 1.7s without changing what the test proves, and reran the fullforge.jsoncheck list (408 tests) clean, plustsc --noEmit.Closes #246