Open jordanrfrazier opened 10 months ago
A few issues:
execution.stop()
code were not being executed (or displayed(?)) execution
lock will simply not work as-is -- the stop
and next
methods both require an owned instance of execution, which locks them out of each other. So, even if the above was fixed, this would cause deadlock on execution. We need to push down the mutex to the output
channel, at least, to allow for the stop signal to be sent concurrently.
There exists a deadlock when running the following: