mirror of
https://github.com/aljazceru/turso.git
synced 2025-12-28 05:24:22 +01:00
67f3e54782
Closes #2165 The following sequence of events is possible: - init_chunk_heap() called - flush() gets called, and all chunks start writing to disk - chunk A status is WriteComplete, so chunk.read() gets called on chunk A - chunk A sets its status to WaitingForRead - some other chunk B is still in WaitingForWrite status after flush() - for this reason, init_chunk_heap() returns IOResult::IO - init_chunk_heap() is called again - we panic because chunk A is in WaitingForRead status So - we just allow WaitingForRead status in init_chunk_heap() instead. This panic was caught thanks to Pedro's IO latency enhancement to the sim! Reviewed-by: Iaroslav Zeigerman (@izeigerman) Closes #2166