A system clock jump no longer gets misreported as Claude Code hanging.
What's wrong with this entry?
The event-loop stall detector now measures elapsed time with a monotonic clock as well as the wall clock, so a system clock jump is no longer reported as a stall.
- New reported fields: monotonic stall duration, clock jump, whether a slow terminal write was blocking, and whether a resume signal (SIGCONT) was seen, meaning the machine had been suspended.
- Reporting is deferred to the next tick so measuring the stall does not lengthen it.
- Runs whenever the detector is started.
monotonic_stall_ms
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Cache-break diagnostics kept in a per-session file
Both mention diagnostic
-
v2.1.248
Diagnostics store gains an alert slot that nothing writes to
Both mention diagnostic
-
v2.1.248
Dedicated error types for plan polling and referral eligibility
Both mention diagnostic