Open MrCroxx opened 10 months ago
The reason of this panic is that madsim needs to know which node is spawn
ing the task. But when a task is dropping, the global context is empty. In other words, madsim doesn't run any task at that time, so it can't know who is spawning the task. This seems to be a bug since this behavior is normal on tokio. But I don't have a clear solution yet.
Let me construct a minimum reproducible example first.
In RisingWave deterministic test, got the following panic, which is caused by
tokio::spawn
when some struct drop during task drop.