The post-merge release run for #885 exposed a load-sensitive timing assertion: the event loop remained non-blocking, but the runner scheduled a 10ms heartbeat after 103ms against an 80ms wall-clock threshold. Replace that clock assertion with worker start/finish events that directly prove the heartbeat executes while the blocking lookup is still running.
Verification: focused test passed 10/10 repeated runs; full suite 1688 passed, 1 skipped.
Closes #884
The post-merge release run for #885 exposed a load-sensitive timing assertion: the event loop remained non-blocking, but the runner scheduled a 10ms heartbeat after 103ms against an 80ms wall-clock threshold. Replace that clock assertion with worker start/finish events that directly prove the heartbeat executes while the blocking lookup is still running.
Verification: focused test passed 10/10 repeated runs; full suite 1688 passed, 1 skipped.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #884
The post-merge release run for #885 exposed a load-sensitive timing assertion: the event loop remained non-blocking, but the runner scheduled a 10ms heartbeat after 103ms against an 80ms wall-clock threshold. Replace that clock assertion with worker start/finish events that directly prove the heartbeat executes while the blocking lookup is still running.
Verification: focused test passed 10/10 repeated runs; full suite 1688 passed, 1 skipped.