-
-
Notifications
You must be signed in to change notification settings - Fork 645
fix(pipstar): fix whl extraction and flip pipstar=true #3461
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
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 flips the default setting for the Highlights
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 correctly enables the pipstar feature by default, which is a significant step forward. The change itself is simple and direct. The accompanying CHANGELOG.md update is clear and provides users with the necessary information to adapt to this change, including how to opt-out. I have one minor suggestion to improve the formatting in the changelog.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
CI failure: |
|
That failure is a bit strange. It would mean there are literally no files under site-packages? |
|
The build query is weird, it seems like a regression to me. |
|
Somewhat something that I thought might be the case, we can't just extract a wheel, we need to map certain paths in a particular way: This is what the data contains in the non pipstar case. |
|
found it, had it forgotten. |
|
@rickeylev, do you wanna do the path remapping at the build time instead of the repo phase? I think that for compatibility reasons we should keep this for now and then we can think about it later on how we can actually extract/link the wheels better. |
|
OK, bugs should have been fixed PTAL. |
|
yes, lets keep it the same for now, for compatibility. |
Attempt number 2. This should be smoother this time and should not cause
any breakage because we are not enabling any cross-building by default and
only the host wheels will be present.
Because we also started extracting using starlark APIs, some extra fixups
where needed because some wheels require extracting
.datafiles intocorrect paths. This also adds the
INSTALLERfile after extracting files tosignify that
pipstarhas installed the file.Because we have stopped passing hermetic interpreter to the
whl_libraryifpipstar is enabled, we also needed to ensure that the code path is only enabled
if the extraction with pipstar is supported (i.e. bazel >= 8).
Fixes #2949