Stream: git-wasmtime

Topic: wasmtime / Issue #1684 Dependabot can't resolve your Rust...

Wasmtime GitHub notifications bot (May 12 2020 at 16:34):

dependabot-preview[bot] opened Issue #1684:

Dependabot can't resolve your Rust dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

error: failed to parse manifest at `/home/dependabot/dependabot-updater/dependabot_tmp_dir/crates/wasi-common/Cargo.toml`

Caused by:
  package `wasi-common v0.16.0 (/home/dependabot/dependabot-updater/dependabot_tmp_dir/crates/wasi-common)` specifies that it links to `wasi-common-16` but does not have a custom build script

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Wasmtime GitHub notifications bot (May 12 2020 at 16:46):

pchickey commented on Issue #1684:

I can close these all day dependabot

Wasmtime GitHub notifications bot (May 12 2020 at 16:46):

pchickey closed Issue #1684:

Dependabot can't resolve your Rust dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

error: failed to parse manifest at `/home/dependabot/dependabot-updater/dependabot_tmp_dir/crates/wasi-common/Cargo.toml`

Caused by:
  package `wasi-common v0.16.0 (/home/dependabot/dependabot-updater/dependabot_tmp_dir/crates/wasi-common)` specifies that it links to `wasi-common-16` but does not have a custom build script

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Wasmtime GitHub notifications bot (May 12 2020 at 16:47):

bjorn3 commented on Issue #1684:

Have you contacted support?

Wasmtime GitHub notifications bot (May 12 2020 at 18:37):

pchickey commented on Issue #1684:

Yes

Wasmtime GitHub notifications bot (May 27 2020 at 10:58):

feelepxyz commented on Issue #1684:

:wave: Hey sorry for the slow response on this, just had a look and seems like it's caused by https://github.com/bytecodealliance/wasmtime/blob/master/crates/wasi-common/Cargo.toml#L17

Dependabot does by design not execute any build scripts and we only clone Cargo manifests and lockfiles so don't have access to everything when running Cargo. Do you know if there's any way of running Cargo and ignoring these linked libraries?

Wasmtime GitHub notifications bot (May 27 2020 at 12:11):

bjorn3 commented on Issue #1684:

Adding a dummy build.rs next to every Cargo.toml containing only fn main() {} may work.

The error is emitted at https://github.com/rust-lang/cargo/blob/d18e4b36e7dd7a02a962d390f9c596a3df9a8d8c/src/cargo/util/toml/mod.rs#L1091-L1100

Wasmtime GitHub notifications bot (May 27 2020 at 14:10):

alexcrichton commented on Issue #1684:

@feelepxyz FWIW that "links" directive doesn't actually link anything, it's just another feature of Cargo's crate graph resolution (one crate per "links" value per graph). Learning about the crate graph, for example with cargo metadata, doesn't actually execute any user code.

Wasmtime GitHub notifications bot (May 28 2020 at 14:53):

feelepxyz commented on Issue #1684:

Adding a dummy build.rs next to every Cargo.toml containing only fn main() {} may work.

Ah yes that seems sensible, will give that a go :+1:

Wasmtime GitHub notifications bot (Jun 01 2020 at 22:09):

pchickey commented on Issue #1684:

@feelepxyz Thanks for getting to this issue. We have disabled dependabot for this repo because the repetitive notifications were getting overwhelming. Can you please let us know if and when a fix for this issue makes it into production, so we can experimentally re-enable on a fork? I also saw in the support ticket that relief from repetitive notifications is in progress, thank you for that.

Last updated: Nov 22 2024 at 17:03 UTC