Closed chuck-dbos closed 2 months ago
The timeout is because the receive workflow has a timeout=10
on recv
. If we see this timeout, it means recv is not properly notified when the message is inserted. I wonder why this never showed up before..
PR looks good. I will investigate the recv bug separately
The printouts on exit were covering cases that didn't warrant any attention (such as importing dbos module without ever making a DBOS), and generated confusion. Removed those as they weren't the interesting ones.
Also removed an assert about how long something takes to run, as it is flaky in the test runner, and was cut+paste from another test, so no reason to have a redundant copy of that assert.