-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Broken test data in valid-service-1.x.json #294
Comments
Thank you very much for the report, @tokcum .
Could you link the fixed version you used? Having the diff as a working "expected input" would help analyze the issue. |
@jkowalleck, great. I've created a PR. |
jkowalleck
pushed a commit
that referenced
this issue
Sep 11, 2023
…ce` (#295) Fixes an inconsistency in test data of valid-service. First experienced in valid-service-1.4.json, other files (other versions and filetypes) showed the same deviation. The fix was derived from working test data of valid-service. closes #294 Signed-off-by: tokcum <[email protected]>
jkowalleck
pushed a commit
to jkowalleck/fork_CycloneDX-specification
that referenced
this issue
Sep 11, 2023
…ce` (CycloneDX#295) Fixes an inconsistency in test data of valid-service. First experienced in valid-service-1.4.json, other files (other versions and filetypes) showed the same deviation. The fix was derived from working test data of valid-service. closes CycloneDX#294 Signed-off-by: tokcum <[email protected]>
jkowalleck
added a commit
to jkowalleck/fork_CycloneDX-specification
that referenced
this issue
Sep 11, 2023
forward-port of CycloneDX#295 fixes CycloneDX#294 in 1.6 Signed-off-by: Jan Kowalleck <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
working on cyclonedx-rust-cargo to support 1.4 I'm experiencing failed integration tests when verifying against valid-service-1.4.json while valid-service-1.4.xml just works.
The error tells me that a dependency references a bom which is not available in the file. Comparing the JSON to the XML file, I found that in JSON, the bom-ref is different. Setting the bom-ref to the value referenced in ref (like it is in XML), the test works fine.
In XML it looks like this:
It looks like this derivation existed from the very beginning of the test data. So, maybe I'm missing something or the implementation in cyclonedx-rust-cargo is stricter than other projects using the spec's test data.
I've prepared a fix in my own fork. If my analysis above is correct, let me know. I will create a pull request. Thanks.
The text was updated successfully, but these errors were encountered: