-
-
Notifications
You must be signed in to change notification settings - Fork 576
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
Unexpected output for field vcs_url in cargo workkspaces #3769
Labels
Comments
@meretp Thanks! Support for Cargo workspace is a recent addition @AyanSinhaMahapatra |
AyanSinhaMahapatra
changed the title
Unexpected output for field vcs_url in package detection
Unexpected output for field vcs_url in cargo workkspaces
May 17, 2024
AyanSinhaMahapatra
added a commit
that referenced
this issue
May 20, 2024
Reference: #3769 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
6 tasks
AyanSinhaMahapatra
added a commit
that referenced
this issue
May 22, 2024
Reference: #3769 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
@meretp this should be fixed with a lot of bugfixes and improvements on cargo workspaces, see #3783 (comment) for details on this. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When scanning /boring-sys/Cargo.toml with the current release of ScanCode I get the following package data detection including an object for the vcs_url. Is this the expected behaviour? From the model definition of a package I would have expected an optional string here. Also, I don't really know how to interpret this value.
There is also a scan_error, maybe this is related to the unexpected output here?
How To Reproduce
This is the command I used, executed within the extracted directory of the latest release downloaded from GitHub.
./scancode -clpu --only-findings -n 20 --license-text --json result_boring_cargo.json ../boring/boring-sys/Cargo.toml
System configuration
The text was updated successfully, but these errors were encountered: