generated from EmbarkStudios/opensource-template
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bug: panic unable to locate testing for crate
#84
Labels
bug
Something isn't working
Comments
Ok I'm pretty sure this is due to overlapping module names. The new module in qdrant is named |
Can you provide a link to a full cargo.toml/workspace that repros this behavior, I'm missing too much context though I know what needs to be fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Cargo panics on a remote git dependency when I run it. The dependency is a git sha in a branch on a public repo (a fork of the original project):
To reproduce
I'm sure there's some part of our cargo.toml or deny config that's useful here, happy to try to extract it if so.
cargo-deny version
cargo-deny 0.14.21
What OS were you running cargo-deny on?
MacOS
Additional context
Here's the relevant portion of the Cargo.toml. I'm updating rust (
nightly-2024-02-24
) and I've updated these dependencies and added a new one oncommon
when doing so. Thesegment
dependency is not new and was working with cargo deny on our previous version of rustThe text was updated successfully, but these errors were encountered: