WorkflowThreadContext has no currentThread in RUNNING state

[dplyukhin]

Expected Behavior

Actual Behavior

A customer reports that WorkflowContext#runUntilBlocked can reach this code path, where the deadlock timeout has elapsed but currentThread hasn't been initialized.

Steps to Reproduce the Problem

Run a worker under high load with virtual threads.

Specifications

• Version:
• Platform:

[dplyukhin]

If I'm understanding correctly, the problem is currentThread doesn't get set until we actually run the task, and the deadlock detection timeout is elapsing before we manage to run it. That could be caused by (a) worker stress I guess, in which case the solution would be to wait a little longer until we get a free carrier thread; but it could also be caused by (b) a deadlock tying up all the carrier threads, in which case we'd never get a chance to run the task. Since we can't distinguish scenario A from scenario B, I think we have to continue crashing the worker. But we can at least improve the error message and update the outdated comment.