-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geiger Failed to match & Failed to parse - Tracker #240
Comments
From https://gitlab.com/schmilblick/violetear/web-api - Example 2Same repro or nightly as well tested as part of #65 From issue #65 using
Additional Resolution
|
tokio/tokio - Example 3 From #13 More failed to match
|
This fixes the issue with `Failed to match` errors, which was caused by cargo-metadata behaviour of not resolving dev-dependencies of crate dependency. Now we check if crate is root and if not, we won't collect dev deps for this package, cause they are anyways not in krates graph, which relies on cargo-metadata `resolve` output field. Also changed argument for `Failed to match` error, cause it mentioned not the real one unmatched package. Relates to geiger-rs#240
#263 by @ilyatrefilov seems to have fixed most Failed to match ones We still have left at git2-rs:
This is probably due to lack of workspace support as the dependency in Cargo.lock comes via workspace member - systest - which we don't add into graph [[package]]
name = "systest"
dependencies = [
..
"ctest",
]
[[package]]
name = "ctest"
version = "0.2.22"
dependencies = [
..
"syntex_syntax2",
]
[[package]]
name = "syntex_syntax2"
version = "0.0.2"
dependencies = [
..
"serde",
"extprim",
]
[[package]]
name = "extprim"
version = "1.7.1"
dependencies = [
..
"serde",
] |
This fixes the issue with `Failed to match` errors, which was caused by cargo-metadata behaviour of not resolving dev-dependencies of crate dependency. Now we check if crate is root and if not, we won't collect dev deps for this package, cause they are anyways not in krates graph, which relies on cargo-metadata `resolve` output field. Also changed argument for `Failed to match` error, cause it mentioned not the real one unmatched package. Relates to #240
I'm also using a workspace and get this in my projects. Can provide info if that would be helpful: ex line:
|
I've fallen behind so my apologies about that. Would you like to do a PR to help work on this ? |
@pinkforest To be honest, I'm not even sure where to start looking. Is there a document somewhere that describes development with this project? I'd be happy to attempt! |
git2-rs - Example 1
Repro
docker run -ti --rm rust /bin/bash
rustc
toolchain
Suspect Errors - Unwanted 1 - Failed to match
Suspect Errors - Unwanted 2 - Failed to parse
Failed to parse file: /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/serde_json-1.0.74/src/features_check/error.rs, Syn(Error("expected one of:
fn,
extern,
use,
static,
const,
unsafe,
mod,
type,
struct,
enum,
union,
trait,
auto,
impl,
default,
macro, identifier,
self,
super,
crate,
::"), "/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/serde_json-1.0.74/src/features_check/error.rs")
Resolution
Investigation
TBD - It all seems to build fine?
The text was updated successfully, but these errors were encountered: