Development build: Trace action computes double traces
When running a development build, opening the trace action sometimes (but not always) causes two traces to be shown because two trace commands are sent to the worker. (This is caused by an effect being invoked twice; the cancellation is not triggered because the state is not updated in-between.) Restarting the trace from the UI works fine.