gazelle() rule fail with custom gazelle_binary about bazel-gazelle

[fmeum]

I can reproduce it now, I was on an older commit when I first tried this.

[mpatou]

Note it's not just custom gazelle_binaryusing what is proposed by rules_python is also not working:

gazelle(
    name = "gazelle",
    data = GAZELLE_PYTHON_RUNTIME_DEPS,
    gazelle = "@rules_python//gazelle:gazelle_python_binary",
)

[fmeum]

If I check out rules_python and update the Gazelle version in examples/build_file_generation to v0.32.0, running bazel run //:gazelle in that directory succeeds. Could you check whether you are using the latest version of rules_python?

[mpatou]

I am. I have a synthetic repro that is a few files only I can upload it somewhere if you want to have a look.

[fmeum]

I can reproduce this with Gazelle up to v0.32.0, but not with v0.33.0. I think that it was fixed by e3deb49.

@aignas It looks like some :gazelle target in rules_python's examples were broken without causing CI failures. In bazel-gazelle, we run the targets explicitly in CI and check that there is no diff for the examples. That could provide additional test coverage.