Vitali Lovich

@Cvolton right but simultaneously it's weird that I'm observing flapping in our CI. I noted the image it seemed like it was working on vs broken which ostensibly in the...

@kishorekumar-anchala no unfortunately i can't. We've switched to windows 2025 because our CI was blocked on this.

Actually this repro even fails on first run. ``` use std::sync::Arc; use lancedb::{arrow::arrow_schema::{DataType, Field, Schema}, connection::ConnectBuilder}; #[tokio::main] async fn main() { let db = ConnectBuilder::new("test.db").execute().await.unwrap(); let schema: Arc = Arc::new(Schema::new(vec![...

Ah, yes. I'm probably not using anything from the lib. Will try again. FWIW the workaround I'm using re feature flag is to have the library have a dev-dependency on...

Here's all I needed to change to make it work: Cargo.toml: ``` [dependencies] divan = { version = "0.1", optional = true } [dev-dependencies] my-crate = { path = ".",...

It's more about a defense in depth strategy since fundamentally there's no way to completely bullet proof catching memory issues due to unsafe & it gets worse when there's a...

Correct. It passes with tmpfs and btrfs and the read fails everywhere else (writes are fine & I've verified using hexdump & breaking before we attempt the read that the...

Is there any debugging tips you can share? I haven't figured out how to figure out why the kernel is responding in this way.

You don't happen to have a a basic C example handy do you? Is https://unixism.net/2020/04/io-uring-by-example-part-1-introduction/ a good starting point?

Haven't tried the repro yet, but one thing I've narrowed it down to is this only happens when the file is created and written to. Then reads start failing. If...