-
-
Notifications
You must be signed in to change notification settings - Fork 663
fix(pipstar): handle a corner case for compatible version evaluation #3583
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(pipstar): handle a corner case for compatible version evaluation #3583
Conversation
It seems that there was one corner case that was left unhandled. In theory we should also handle `3 ~= 3.0.0`, but the fix for that may be a little more involved and I want to leave it for later. Fixes bazel-contrib#3580
Summary of ChangesHello @aignas, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on refining the version comparison logic within pipstar to better align with PEP440 standards. It resolves a specific edge case related to compatible version specifiers and includes a new test case to ensure comprehensive coverage across different Python versions. The changes also involve refactoring the code for improved clarity and maintainability. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request successfully addresses a corner case in compatible version evaluation (~=) to improve compatibility with the PEP440 standard, introducing new helper functions _is_prefix and _left_is_prefix and integrating them into _version_compatible with new test cases. However, a medium-severity Denial of Service (DoS) vulnerability was identified in python/private/version.bzl due to a lack of input length validation on version strings, which could lead to excessive resource consumption. Remediation has been recommended.
…3583) It seems that there was one corner case that was left unhandled. In theory we should also handle `3 ~= 3.0.0`, but the fix for that may be a little more involved and I want to leave it for later. However, that case is unlikely to occur in reality because `LHS` for our cases will most likely have 2 components. Whilst at it prepare for the patch release (#3584). Fixes #3580 (cherry picked from commit a32c744)
It seems that there was one corner case that was left unhandled.
In theory we should also handle
3 ~= 3.0.0, but the fix for that maybe a little more involved and I want to leave it for later. However,
that case is unlikely to occur in reality because
LHSfor our caseswill most likely have 2 components.
Whilst at it prepare for the patch release (#3584).
Fixes #3580