Query evaluation against outdated version of entity in nested component removal requests about miniplex HOT 2 OPEN

I'm having a similar issue, it seems to be a race condition with removing and reindexing:
When removing an entity from the world, some onRemoved subscribers will try to do some cleanup and run a world.removeComponent. This will reindex the removed component, adding it back to any buckets it was just removed from. Then world.remove will finish and the entity will no longer be in the world bucket. so each loop of a system, when I pull something out of a query I have to check if the entity is still in the world and if not I remove it from the bucket.

There should be a way to skip reindexing entities that are being removed from the root world bucket

Otherwise the library has been very helpful =D

from miniplex.

I'm assuming these are two separate (even if similar sounding) issues -- would you be willing to provide a (failing) test case? I'd be happy to fix and improve these situations, but I need to better understand what's going on.

In the meantime, it sounds like a potential workaround for these issues would be to queue the follow-up work (like removing the second component) using queueMicrotask.

from miniplex.