smarm

Files

T

Claude 7bab4d23ea fix(scheduler): entry-side check_cancelled in park_current — stop against a QUEUED actor was lossy

request_stop sets the flag and issues a wildcard unpark, but unpark
no-ops on a Queued actor (the pending run "is" the wake). If the
actor's first action on resume is a blocking park — no allocation, no
check!() on the way — the wake-side-only check in park_current is
unreachable: the actor parks with the stop flag already set and no
wake is ever coming. The runtime then idles forever.

Fix: check_cancelled at the ENTRY of park_current, before the switch.
The remaining window (flag lands after the entry check, before the
park) is covered by the existing protocol: the stop's unpark finds
Running / the prep-to-park window, sets Notified, and the park-return
re-queues into the wake-side check. Unwinding from the entry is the
same unwind path as the wake side; leftover wait registrations are
stale-epoch / dead-generation and self-clean at their wakers' failed
CAS.

This is bug #1 of the urus chunk-2 session (bug #2, the terminal
wake, is the preceding commit). Repro: tests/cancel.rs
stop_flagged_while_queued_lands_at_first_park — deadlocks without the
fix (watchdog-bounded), passes in <50ms with it.

2026-06-11 21:15:03 +00:00

actor.rs

feat(runtime): phase 2 — fixed slab, per-slot packed-atomic state machine, raw cold locks

2026-06-09 20:08:12 +00:00

channel.rs

feat(select): fd arms in select + timed fd waits (RFC 008 phase 1)

2026-06-11 11:28:58 +00:00

context.rs

docs(context): fix off-by-one-slot error in init_actor_stack layout comment

2026-05-28 05:50:18 +00:00

gen_server.rs

feat(gen_server): handle_down — runtime monitor forwarding via ServerCtx/Watcher