-
Notifications
You must be signed in to change notification settings - Fork 541
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
Error when pip.parse.experimental_index_url
is a private index
#2033
Comments
@dougthor42, could you see if main works differently? #2017 should help with debugging at least. |
Sorry I didn't put that front-and-center - it's hidden at the bottom of "Anything else relevant". When running on
|
This does look like the gazelle plugin got removed during testing with main. It does not make sense that overriding rules_python would cause this. Unless you overrode both, gazelle and rules_python and we have a much bigger issue with the plugin.
I am slightly confused.
On the original topic though, the behaviour is different if your private index has some packages that have the same name as the public index, but the sha256 values in the private index are not the ones that your lock file is requesting.
This is my only idea why you would see any difference in behaviour.
…On 4 July 2024 08:27:40 GMT+09:00, Douglas Thor ***@***.***> wrote:
> could you see if main works differently?
Sorry I didn't put that front-and-center - it's hidden at the bottom of "Anything else relevant". When running on `main`, _both_ cases result in:
```
ERROR: no such package '@@[unknown repo 'com_github_bazelbuild_rules_go' requested from @@rules_python_gazelle_plugin~]//go/runfiles': The repository '@@[unknown repo 'com_github_bazelbuild_rules_go' requested from @@rules_python_gazelle_plugin~]' could not be resolved: No repository visible as ***@***.***_github_bazelbuild_rules_go' from repository '@@rules_python_gazelle_plugin~'
ERROR: /usr/local/google/home/dthor/dev/pyle/BUILD.bazel:81:24: no such package '@@[unknown repo 'com_github_bazelbuild_rules_go' requested from @@rules_python_gazelle_plugin~]//go/runfiles': The repository '@@[unknown repo 'com_github_bazelbuild_rules_go' requested from @@rules_python_gazelle_plugin~]' could not be resolved: No repository visible as ***@***.***_github_bazelbuild_rules_go' from repository '@@rules_python_gazelle_plugin~' and referenced by '//:gazelle_python_manifest.test'
ERROR: Analysis of target '//:gazelle_python_manifest.test' failed; build aborted: Analysis failed
INFO: Elapsed time: 9.454s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
```
--
Reply to this email directly or view it on GitHub:
#2033 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
I did play it fast and loose with the |
Thanks, see you next week then. :)
…On 4 July 2024 08:51:43 GMT+09:00, Douglas Thor ***@***.***> wrote:
I _did_ play it fast and loose with the `git_override` when I was testing `main`. It's possible I f'd something up haha. We've got a long weekend coming up so you might not hear back until July 8th/9th.
--
Reply to this email directly or view it on GitHub:
#2033 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
OK here's more info: TL;DR: It looks like commit b4b52fc (#1917) is the culprit, and it was fixed in 11133b3 (#2017). It looks like (a) my The rest of this comment is kept for my own sanity and reference. Feel free to ignore. ProcedureTo test, I chose a semi-random target and would run tests:
I cloned I also went back to 0.32.0, when So I Lastly, because I only realized at the end that I forgot to Results Table:
How I patched:# in MODULE.bazel
local_path_override(
module_name = "rules_python",
path = "/usr/local/google/home/dthor/dev/rules_python",
)
local_path_override(
module_name = "rules_python_gazelle_plugin",
path = "/usr/local/google/home/dthor/dev/rules_python/gazelle",
) `Error: 'string' object is not callable'
|
It was correct, but #2057 was preventing it from working correctly. 🙃 |
Thanks for the thorough investigation and the new ticket! |
🐞 bug report
Affected Rule
pip.parse
Is this a regression?
No. From what I can tell, it's always been present since
experimental_index_url
was added.Description
Something wonky goes on when using a private index as the default pip index url. It seems like the credential helper is not working, but that may be a red herring.
🔬 Minimal Reproduction
This is fine:
This fails:
🔥 Exception or Error
🌍 Your Environment
Operating System:
gLinux
Output of
bazel version
:We're using 7.2.0rc1 because of bazelbuild/bazel#22664 which is actually a bug with
jupyter/testpath
that I haven't made apip.override
for yet.Rules_python version:
Confirmed with:
Anything else relevant?
The text was updated successfully, but these errors were encountered: