Tokio unstable from app to deps

[hardy hound]

Hi, I have a local crate, which enable tokio unstable, through it's config file. I can build it successfully with wasi as target. .
I get an app which enable tokio unstable too, and use the local crate as dependency.
But I get

use of unstable library feature `wasi`
    --> /data/data/com.termux/files/home/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.47.1/src/net/tcp/stream.rs:1427:9

If I run cargo tree -i tokio , the only deps which depend on is my local crate.
I miss something on my app?

I use rust nightly

[signal solar]

How did you enable tokio_unstable?

[hardy hound]

[build]                                   rustflags = ["--cfg", "tokio_unstable"]

Into .cargo/config.toml

[signal solar]

It sounds like the extra dependency enabled Tokio's net feature, which when combined with tokio_unstable, requires nightly on wasi ... probably.

[hardy hound]

Nightly on wasi?

Rust nightly?

[signal solar]

Hmm

We use

use std::os::wasi::prelude::*;

the only unstable thing there is fs

but we don't use fs

seems weird

[hardy hound]

FYI I use a patched version of tokio which include https://github.com/tokio-rs/tokio/pull/6893

I don't use tokio::fs

[signal solar]

Then that's why.

uhm

You need to use [patch.crates-io]. Otherwise you will have multiple incompatible copies of Tokio.
See: https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html

either way, it's likely that this PR requires nightly

[hardy hound]

Ah perfect, I didn't patch my app only dependencies