In reply to @9hp71n:matrix.org

This could be some way of doing second thing:

helix-unwrapped = inputs.helix.packages.x86_64-linux.helix-unwrapped.overrideAttrs(old: {
    cargoArtifacts = old.cargoArtifacts // { cargoExtraArgs = "--locked --features unicode-lines"; };
    cargoExtraArgs = "--locked --features unicode-lines";
} );

probably third too or using cargoBuildCommand instead.
Not sure if works, did not build myself and not sure how you would check if feature is there.
And also after that you would need to find a way to wrap resulting helix-unwrapped

Hey, I'm packaging https://github.com/golemcloud/golem using buildRustPackage and one of its dependencies is using cargo_metadata (https://github.com/oli-obk/cargo_metadata) to get another dependency-crates source location to get to its protobuf directory. However when cargo_metadata is called it fails with the following error here: https://github.com/golemcloud/wasm-rpc/blob/97cefa99408b89d12ed13f2dd6333df01c12666d/wasm-rpc/build.rs#L26-L29)

with the following error:

golem>   error: failed to get `arbitrary` as a dependency of package `golem-wasm-rpc v0.0.0 (/build/cargo-vendor-dir/golem-wasm-rpc-0.0.0)`
golem>   Caused by:
golem>     failed to load source for dependency `arbitrary`
golem>   Caused by:
golem>     Unable to update registry `crates-io`
golem>   Caused by:
golem>     failed to update replaced source registry `crates-io`
golem>   Caused by:
golem>     failed to read root of directory source: /build/cargo-vendor-dir/cargo-vendor-dir
golem>   Caused by:
golem>     No such file or directory (os error 2)
golem>   thread 'main' panicked at /build/cargo-vendor-dir/golem-wasm-rpc-0.0.0/build.rs:30:10:
golem>   called `Result::unwrap()` on an `Err` value: CargoMetadata { stderr: "" }

I don't understand why it would resolve to the path:

golem>     failed to read root of directory source: /build/cargo-vendor-dir/cargo-vendor-dir
golem>   Caused by:
golem>     No such file or directory (os error 2)

In reply to @marijan:matrix.org

Hey, I'm packaging https://github.com/golemcloud/golem using buildRustPackage and one of its dependencies is using cargo_metadata (https://github.com/oli-obk/cargo_metadata) to get another dependency-crates source location to get to its protobuf directory. However when cargo_metadata is called it fails with the following error here: https://github.com/golemcloud/wasm-rpc/blob/97cefa99408b89d12ed13f2dd6333df01c12666d/wasm-rpc/build.rs#L26-L29)

with the following error:

golem>   error: failed to get `arbitrary` as a dependency of package `golem-wasm-rpc v0.0.0 (/build/cargo-vendor-dir/golem-wasm-rpc-0.0.0)`
golem>   Caused by:
golem>     failed to load source for dependency `arbitrary`
golem>   Caused by:
golem>     Unable to update registry `crates-io`
golem>   Caused by:
golem>     failed to update replaced source registry `crates-io`
golem>   Caused by:
golem>     failed to read root of directory source: /build/cargo-vendor-dir/cargo-vendor-dir
golem>   Caused by:
golem>     No such file or directory (os error 2)
golem>   thread 'main' panicked at /build/cargo-vendor-dir/golem-wasm-rpc-0.0.0/build.rs:30:10:
golem>   called `Result::unwrap()` on an `Err` value: CargoMetadata { stderr: "" }

I don't understand why it would resolve to the path:

golem>     failed to read root of directory source: /build/cargo-vendor-dir/cargo-vendor-dir
golem>   Caused by:
golem>     No such file or directory (os error 2)

In reply to @julius:mtx.liftm.de
sent a file.

In reply to @marijan:matrix.org
Can you point me to the relevant code? what do you mean with patching it with placeholder on cargoDeps?

In reply to @julius:mtx.liftm.de
I'm running rust-analyzer from nixos-unstable on a rust project that is mostly a blank project with cargo add matrix-sdk. And I get 100eds of cargo-auditable processes.