-
Notifications
You must be signed in to change notification settings - Fork 443
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
fix: create new version comparison function #3470
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3470 +/- ##
==========================================
- Coverage 78.32% 78.23% -0.09%
==========================================
Files 760 761 +1
Lines 11497 11560 +63
Branches 1343 1356 +13
==========================================
+ Hits 9005 9044 +39
- Misses 2053 2099 +46
+ Partials 439 417 -22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This new implementation passes all tests now, which is satisfying but also makes me suspicious that I need more tests because there's definitely cases I know I'm missing. |
Had to fix kerberos reporting. For some reason we were expecting 10 vulns, but even cvedetails is reporting 9 for this version: |
Updating the branch just for the cve-scan job (which was fixed by specifying a version of python) |
We had been using packaging's version parsing tools, but as they move more towards pep440 compliance they aren't as useful for comparing arbitrary versions that may not follow the same scheme. This moves us to our own function. It may need some further tweaking for special cases such as release candidates or dev versions. Signed-off-by: Terri Oda <terri.oda@intel.com>
Signed-off-by: Terri Oda <terri@toybox.ca>
a544a55
to
8044a05
Compare
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.
Okay, I think I've resolved everything except the pre-check function idea. I think I might open a separate issue for that and let someone else work on it, if you don't mind. (Mostly because I don't want to take up more of your time and it's been ahrd to find someone to review this code as is...)
Thanks @antoniogi -- I'm very glad to have had a fresh set of eyes on this. |
We had been using packaging's version parsing tools, but as they move more towards pep440 compliance they aren't as useful for comparing arbitrary versions that may not follow the same scheme. This moves us to our own function. It may need some further tweaking for special cases such as release candidates or dev versions.
This is a replacement for #3430 because cmp_version didn't work out as well as I'd hoped.