the current invocation is "top level", subsequently clearing out the accumulated TX queue and returning (original behavior)
some other thread is clearing the TX queue, in which case it just spins and awaits completion of processing on the other thread
To compliment this, the depth tracking changed a little to include information about which thread is currently running the queue, which is required to prevent deadlocks.
Verified in our current test suite to greatly improve reproducibility.
This changes
submit-sync-tx!to block ifTo compliment this, the depth tracking changed a little to include information about which thread is currently running the queue, which is required to prevent deadlocks.
Verified in our current test suite to greatly improve reproducibility.