BuildOwner.buildScope() now requeues the rebuilds a failed pass never reached
and requests a frame before rethrowing, so a host that survives the error
drains that work on its next pass.
What is not established is what happens when nothing catches it. _drawFrame
and the scheduler have no catch, so in an ordinary session the error escapes
a timer callback. What the terminal looks like afterwards — raw mode, the
alternate screen, mouse reporting, the cursor — has not been checked, and the
fix above is only reachable by a host that keeps running.
Answering this needs a real terminal session, which is outside ordinary
verification here, so it needs its own authorization. Until then the honest
summary is the one in the 0.0.3 changelog: the fix helps a guarded zone and a
test, and says nothing about an uncaught build error in a live terminal.
BuildOwner.buildScope()now requeues the rebuilds a failed pass never reachedand requests a frame before rethrowing, so a host that survives the error
drains that work on its next pass.
What is not established is what happens when nothing catches it.
_drawFrameand the scheduler have no
catch, so in an ordinary session the error escapesa timer callback. What the terminal looks like afterwards — raw mode, the
alternate screen, mouse reporting, the cursor — has not been checked, and the
fix above is only reachable by a host that keeps running.
Answering this needs a real terminal session, which is outside ordinary
verification here, so it needs its own authorization. Until then the honest
summary is the one in the 0.0.3 changelog: the fix helps a guarded zone and a
test, and says nothing about an uncaught build error in a live terminal.