-
Notifications
You must be signed in to change notification settings - Fork 235
Add setuptools_scm #1749
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
Add setuptools_scm #1749
Conversation
Reviewer's GuideThe PR updates the CUDA container build script to include setuptools_scm in the installation pipeline, ensuring version metadata is generated correctly during CUDA image builds. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
Summary of Changes
Hello @ericcurtin, 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 updates the build script for the CUDA container image to include setuptools_scm
as a required dependency. This change ensures that projects built within the CUDA environment can properly manage their versioning using source control metadata.
Highlights
- Dependency Addition: Added
setuptools_scm
as a new dependency for the CUDA container build process.
Using Gemini Code Assist
The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
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 .gemini/
folder in the base of the repository. Detailed instructions can be found here.
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 or fill out our survey to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Hey @ericcurtin - I've reviewed your changes and they look great!
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
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 adds setuptools_scm
as a dependency for the CUDA container build. While the intent is clear, the current implementation introduces a bug by misusing a helper function in the build script. My review identifies this critical issue, which would cause the build to fail, and provides a direct code suggestion to fix it, along with an alternative approach for better consistency.
@@ -106,6 +106,7 @@ pip_install_all() { | |||
pip_install requirements/cpu-build.txt | |||
pip_install requirements/cpu.txt | |||
elif [ "$containerfile" = "cuda" ]; then | |||
pip_install setuptools_scm |
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.
The pip_install
function is designed to install packages from a requirements file, as it uses the -r
flag internally (see line 92: uv pip install -v -r "$1" ...
).
Calling it with a package name like setuptools_scm
instead of a file path will cause the build to fail.
To fix this, you should install the package directly using uv pip install
.
As an alternative for better consistency with the CPU build path, you could consider creating a requirements/cuda-build.txt
file, adding setuptools_scm
to it, and then calling pip_install requirements/cuda-build.txt
here.
pip_install setuptools_scm | |
uv pip install setuptools_scm |
Signed-off-by: Eric Curtin <[email protected]>
LGTM |
Summary by Sourcery
Build: