IssueTracker

We couldn't come up with a simple repro yet - seems like a race condition. I noticed this after some refactoring in this CL, the repro is basically:

1. We have a snapshotFlow collected inside the node scope

2. We mutate state read by the node scope inside onDetach() of a different node

3. After onDetach() callbacks we cancel the node scope

4. The snapshotFlow executes the block after this change, even though currentCoroutineContext().isActive was false inside snapshotFlow.