-
Notifications
You must be signed in to change notification settings - Fork 547
feat: Add XML schema validation (Fixes #1507) #1544
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
Conversation
Resync repository
chore: update pre-commit config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't conventional commits follow type: commit message
instead of [type] commit message
?
test/test_sbom.py
Outdated
# Demonstrate that validation of XML file against schema results in no data | ||
# if file does not match schema or if xml data is parsed against wrong type of sbom | ||
# (indicated by validate being set to False) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be better to use docstrings instead of comments according to PEP8.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BreadGenie - Thanks I have fixed my conventional commits formatting error and I will; update comments to PEP8 convention later and resubmit pull request
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one was also affected by my bad CI update. Could you rebase to origin/main so I'm sure the tests are running correctly in CI?
…n-tool into pr-1507
Erroneous inclusion
@terriko Is this failure another NVD access issue ? I can't get it to fail on the copy on my local machine. |
Looks like the defaults PR caused a conflict with this one. Sorry! But yes, I think the failure in longtests was due to NVD rate limit. If I could only make it through my PRs and get to the point of fixing stuff myself... I think I'll have have to prioritize the CI NVD Key enablement later this week. |
Codecov Report
@@ Coverage Diff @@
## main #1544 +/- ##
==========================================
+ Coverage 81.44% 83.35% +1.90%
==========================================
Files 290 291 +1
Lines 5811 5859 +48
Branches 957 963 +6
==========================================
+ Hits 4733 4884 +151
+ Misses 856 754 -102
+ Partials 222 221 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
Failure on CVE scan is probably due to the extra newline in |
I think this is ready to go, but it's still failing more tests than main is (main is only failing quiet_mode). I've updated the branch to main and hopefully that should clean up the problem? |
Pinging @anthonyharrison -- looks like we've got a version conflict that looks beyond what I should be resolving in the web interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs conflict in version_scanner resolved.
@anthonyharrison I've taken a stab at resolving the merge conflict (it was some type checking stuff) but it looks like I broke something. (edit: looks like the tests finally ran, but some things definitely broke. I'm going to re-run a few of them because it's unclear to me why documentation, for example, didn't pass.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the tests are happy again. Thanks!
No description provided.