You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wrong Gazelle mappings after upgrading to 1.8 #3528
What about 1.8.1 plugin version and 1.8.1rules_python version? There was a bug in how dependencies are resolved with 1.8.1 and I would like to exclude this possibility.
What about 1.8.1 plugin version and 1.8.1rules_python version? There was a bug in how dependencies are resolved with 1.8.1 and I would like to exclude this possibility.
That's the combination I tried initially, and it failed.
The only combination I haven't tried is gazelle plugin 1.8.1, and older rules_python.
cc @thejcannon, in case you have any ideas about this.
I can try and take a look this weekend (but no promises, we got a winter storm blowing through Texas. It's bad enough our most notable elected official is bravely running away, away).
You're right to suspect the parallel wheel scraping change though! I'm guessing something to do with ordering and namespace packages.
I can confirm this. What happens is that simplify runs on individual wheels instead of the merged mapping, which collapses what would be entries for all the child modules into a single entry for the top-level package. This results in merging then picking a single arbitrary wheel for everything in that package.
Activity
aignas commentedon Jan 22, 2026
Does it work if you keep gazelle plugin at 1.6 but rules_python at 1.8.1?
psalaberria002 commentedon Jan 22, 2026
Yes, it does. We managed to update rules_python to 1.8.1 independently. No diff in the gazelle_python.yaml
aignas commentedon Jan 23, 2026
What about
1.8.1plugin version and1.8.1rules_pythonversion? There was a bug in how dependencies are resolved with1.8.1and I would like to exclude this possibility.psalaberria002 commentedon Jan 23, 2026
That's the combination I tried initially, and it failed.
The only combination I haven't tried is gazelle plugin 1.8.1, and older rules_python.
aignas commentedon Jan 23, 2026
If you revert #3415 in
gazelledoes it work?To be honest, this is the only recent change that touches this code.
Since older gazelle and latest
rules_pythonworks, then it seems to be OK to not try gazelle 1.8.1 and olderrules_python.aignas commentedon Jan 23, 2026
cc @thejcannon, in case you have any ideas about this.
arjantop-cai commentedon Jan 23, 2026
Another example with
agnoandagno_aws:1.6.1:1.8.1:rules
1.8.1+ gazelle1.6.1worksrules
1.8.1+ gazelle1.8.1does not workthejcannon commentedon Jan 23, 2026
I can try and take a look this weekend (but no promises, we got a winter storm blowing through Texas. It's bad enough our most notable elected official is bravely running away, away).
You're right to suspect the parallel wheel scraping change though! I'm guessing something to do with ordering and namespace packages.
gholms commentedon Aug 28, 2026
I can confirm this. What happens is that simplify runs on individual wheels instead of the merged mapping, which collapses what would be entries for all the child modules into a single entry for the top-level package. This results in merging then picking a single arbitrary wheel for everything in that package.
fix(gazelle): fix module map for old-style namespaces (bazel-contrib#…
fix(gazelle): fix module map for old-style namespaces (#4135)