Maximilian Roos

> Or you guys can follow the the issue and use the C disk? This looks more complicated than we're hoping for — we're not really testing duckdb, we're testing...

FWIW — and very possibly this is necessary, duckdb is a big project — but duckdb-rs does use lots of space! In PRQL, after `cargo clean && cargo build --features=test-dbs`:...

FYI we're getting [disk space errors in GHA on ubuntu now](https://github.com/PRQL/prql/actions/runs/6115782757/job/16601828219?pr=3480#step:15:45): ``` warning: ar: /home/runner/work/prql/prql/target/x86_64-unknown-linux-gnu/debug/build/libduckdb-sys-fe973d02cdbe21fe/out/libduckdb.a: No space left on device ``` Running the command locally: ``` CARGO_INCREMENTAL=0 cargo doc --features=test-dbs-external...

Sorry for the lack of description. My claim is that attempting to use the library with the minimum possible dependencies in `Cargo.toml` doesn't work. That's what https://crates.io/crates/cargo-minimal-versions attempts to validate...

> Very hard to find the clue to fix the issue OK, though is it: > So maybe it's worth attempting to upgrade `flake2` or transitively raising upstream?

In #135 I see the test failing because nightly isn't installed...

What do you see if you run this, but replacing `gcc` with the location of the new failure? > When I run `cargo +nightly update -Z minimal-versions` to set the...

> https://github.com/wangfenjin/duckdb-rs/actions/runs/4395501064/jobs/7697404026 It looks like this is coming from the arrow crate. What requires that dependency?

I put an issue into arrow: https://github.com/apache/arrow-rs/issues/3849

`arrow-rs` has the same issue when running the steps on their repo — so it is an issue there too!