-
Notifications
You must be signed in to change notification settings - Fork 314
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
Failing to analyze - with Cargo failed to resolve dependencies for path 'rust-client/Cargo.toml': NoSuchElementException: Collection contains no element matching the predicate. #8480
Comments
Thanks for the report! I believe to know what the problem is. But just to double-check, which version of Cargo are you using? |
Which one i use generally for development or which one is in use by this action? |
Nevermind, I've found out that the issue is caused by a change of package IDs in Cargo 1.77. I'll work on a fix. For now, downgrading to Cargo 1.76 works around the issue. |
Thanks a lot. Will be happy to know when this issue is fixed. |
Instead of determining projects based on Cargo's internal package ID, use the `source` propery which is `null` for local code. Fixes #8480. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
ORT will use whatever tool version is available in the environment. In any case, #8497 is supposed to fix this specific issue, but as a follow-up I'm running into redis-rs/redis-rs#1143 and a variant of the issue that #6533 tries to address. |
Instead of determining projects based on Cargo's internal package ID, use the `source` property which is `null` for local code. Fixes #8480. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
Instead of determining projects based on Cargo's internal package ID, use the `source` property which is `null` for local code. Fixes #8480. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
Instead of determining projects based on Cargo's internal package ID, use the `source` property which is `null` for local code. Fixes #8480. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
When running analyze on our project with githubactions we get
07:49:06.333 [DefaultDispatcher-worker-2] ERROR org.ossreviewtoolkit.analyzer.PackageManager - Cargo failed to resolve dependencies for path 'rust-client/Cargo.toml': NoSuchElementException: Collection contains no element matching the predicate.
Error.The error doesn't indicate which dependency exactly it fails on, but even when trying to remove each dependency at a time and also all of the dependencies the error keep occurring, even with an empty file.
Iv'e tried to both use ORT from source and both using gradlew, both are failing the same.
The issue started about a week+ ago without any changes to the relevant files from our side.
Our project: glide-for-redis
Cargo.toml:
The actions:
Iv'e tried:
Make sure that locale lang is fine.
Generating cargo.lock before analyzing.
Removing any comments from cargo file.
Sync submuodoles.
Deleting each dependencies at a time, and all of them together.
And more..
Any help or hint will be great.
Thanks!
The text was updated successfully, but these errors were encountered: