Skip to content

Wrong Gazelle mappings after upgrading to 1.8 #3528

Closed

Description

@psalaberria002

We are seeing a wrong change for a specific dependency in gazelle_python.yaml after upgrading the Gazelle plugin from 1.6 to 1.8.1.

Image
# requirements.in
bosdyn-client==5.0.1.2
bosdyn-orbit==5.0.1.2

Build error:

E   ModuleNotFoundError: No module named 'bosdyn.client'

I suspect it was introduced by https://github.com/bazel-contrib/rules_python/pull/3415/changes

Adding manual resolve directives solves the build errors, but that's just a workaround.

# gazelle:resolve py bosdyn.api @python_deps//bosdyn_api
# gazelle:resolve py bosdyn.bddf @python_deps//bosdyn_core
# gazelle:resolve py bosdyn.client @python_deps//bosdyn_client
# gazelle:resolve py bosdyn.deprecated @python_deps//bosdyn_core
# gazelle:resolve py bosdyn.geometry @python_deps//bosdyn_core
# gazelle:resolve py bosdyn.util @python_deps//bosdyn_core

Activity

  1. aignas commented on Jan 22, 2026

    @aignas
    Collaborator

    Does it work if you keep gazelle plugin at 1.6 but rules_python at 1.8.1?

  2. psalaberria002 commented on Jan 22, 2026

    @psalaberria002
    Author

    Does it work if you keep gazelle plugin at 1.6 but rules_python at 1.8.1?

    Yes, it does. We managed to update rules_python to 1.8.1 independently. No diff in the gazelle_python.yaml

  3. aignas commented on Jan 23, 2026

    @aignas
    Collaborator

    What about 1.8.1 plugin version and 1.8.1 rules_python version? There was a bug in how dependencies are resolved with 1.8.1 and I would like to exclude this possibility.

  4. psalaberria002 commented on Jan 23, 2026

    @psalaberria002
    Author

    What about 1.8.1 plugin version and 1.8.1 rules_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.

  5. aignas commented on Jan 23, 2026

    @aignas
    Collaborator

    If you revert #3415 in gazelle does it work?

    To be honest, this is the only recent change that touches this code.

    Since older gazelle and latest rules_python works, then it seems to be OK to not try gazelle 1.8.1 and older rules_python.

  6. added theissue type on Jan 23, 2026
  7. aignas commented on Jan 23, 2026

    @aignas
    Collaborator

    cc @thejcannon, in case you have any ideas about this.

  8. arjantop-cai commented on Jan 23, 2026

    @arjantop-cai

    Another example with agno and agno_aws:

    1.6.1:

        agno: agno_aws
        agno.agent: agno
        agno.api: agno
        agno.cloud.aws.base: agno
        agno.cloud.aws.s3: agno
        agno.compression: agno
        agno.culture: agno
        agno.db: agno
        agno.debug: agno
        agno.eval: agno
        agno.exceptions: agno
        agno.filters: agno
        agno.guardrails: agno
        agno.hooks: agno
        agno.integrations: agno
        agno.knowledge: agno
        agno.media: agno
        agno.memory: agno
        agno.models: agno
        agno.os: agno
        agno.reasoning: agno
        agno.run: agno
        agno.session: agno
        agno.table: agno
        agno.team: agno
        agno.tools: agno
        agno.tracing: agno
        agno.utils: agno
        agno.vectordb: agno
        agno.workflow: agno
    

    1.8.1:

       agno: agno_aws
    

    rules 1.8.1 + gazelle 1.6.1 works
    rules 1.8.1 + gazelle 1.8.1 does not work

  9. thejcannon commented on Jan 23, 2026

    @thejcannon
    Contributor

    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.

  10. gholms commented on Aug 28, 2026

    @gholms
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    gazelleGazelle plugin related issues

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions