Is `Cargo.toml` current? about duckdb-rs HOT 17 OPEN

Could you give more details? I can’t understand the title, and also the description seems not related to this repo?

from duckdb-rs.

If you wanna know is this repo use the latest version dependencies, yes we are, we always keep them up to date https://deps.rs/repo/github/wangfenjin/duckdb-rs

from duckdb-rs.

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 — that if Cargo.lock is the same as Cargo.toml, does the library still compile?

When I run cargo +nightly update -Z minimal-versions to set the minimum versions allowed, and then cargo tree -i gcc and look for gcc, which seems to be the cause of the error, I find:

gcc v0.3.0
[build-dependencies]
└── miniz-sys v0.1.7
    └── flate2 v1.0.0
        [build-dependencies]
        └── libduckdb-sys v0.7.1 (/Users/maximilian/workspace/duckdb-rs/libduckdb-sys)
            └── duckdb v0.7.1 (/Users/maximilian/workspace/duckdb-rs)

So maybe it's worth attempting to upgrade flake2 or transitively raising upstream?

from duckdb-rs.

Trying to fix the issue, but seems another error reported in arrow pkg.

To be honest, the error message from this tool is totally UN-understandable...Very hard to find the clue to fix the issue

from duckdb-rs.

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?

from duckdb-rs.

I already fix this issue in #135

There report another one in arrow-rs, could you help identify the issue?

run in https://github.com/apache/arrow-rs

cargo minimal-versions test

from duckdb-rs.

I run this command in my project and in arrow-rs project, both report the same error

from duckdb-rs.

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

from duckdb-rs.

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 minimum versions allowed, and then cargo tree -i gcc and look for gcc, which seems to be the cause of the error, I find:

from duckdb-rs.

Updated the CI, but it will fail because I check the result locally

you can clone the arrow-rs or #135 branch

from duckdb-rs.

https://github.com/PRQL/prql/actions/runs/4395201277/jobs/7696819175

You can also check your pipeline log

from duckdb-rs.

https://github.com/wangfenjin/duckdb-rs/actions/runs/4395501064/jobs/7697404026

from duckdb-rs.

Any clue how to fix this?

from duckdb-rs.

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?

from duckdb-rs.

I put an issue into arrow: apache/arrow-rs#3849

from duckdb-rs.

The issue is I'm not sure it's their problem or it's because I misuse it. For the first issue reported of flate2 or gcc, actually it's our cargo.toml don't make the flate2 as optional

That's why I said the error message is too misleading

from duckdb-rs.

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

from duckdb-rs.