You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
buffdb: crate-location/target/debug/build/libduckdb-sys-2e3bca8a7143e85a/out/duckdb/src/storage/storage_manager.cpp:66: int64_t duckdb::StorageManager::GetWALSize(): Assertion `!FileSystem::Get(db).FileExists(GetWALPath())' failed.[1] 1934602 IOT instruction (core dumped) cargo run --all-features -- run
This occurs after I insert data and then immediately try to fetch it back. The two queries are executed over the same connection (but plausibly different threads). Adding a nontrivial delay helps but very much does not guarantee success.
The error is not reliable; I'd estimate it occurs roughly half of the time. Even when this error does not occur, the newly-inserted row is not found nearly every time. Manual verification after the fact confirms that the row was inserted. DuckDB also tries to read out of bounds:
DuckDB failure: Error code 1: Unknown error code Some("IO Error: Could not read enough bytes from file \\"store.db\\": attempted to read 262144 bytes from location 1060864")
I have not the slightest clue if these are related. I am happy to split these out into separate issues if preferred. The queries being executed are as simple as they get, so I've no idea what's going on.
The text was updated successfully, but these errors were encountered:
This occurs after I insert data and then immediately try to fetch it back. The two queries are executed over the same connection (but plausibly different threads). Adding a nontrivial delay helps but very much does not guarantee success.
The error is not reliable; I'd estimate it occurs roughly half of the time. Even when this error does not occur, the newly-inserted row is not found nearly every time. Manual verification after the fact confirms that the row was inserted. DuckDB also tries to read out of bounds:
I have not the slightest clue if these are related. I am happy to split these out into separate issues if preferred. The queries being executed are as simple as they get, so I've no idea what's going on.
The text was updated successfully, but these errors were encountered: