Fabian Meumertzheim

Results 1695 comments of Fabian Meumertzheim

Is it possible that something brings in go_repository repos in your remaining WORKSPACE file? That's not supported when mixed with Bzlmod.

We can't apply overrides to `bazel_dep`s, so we do fall back to using the `go_repository` instead if the user defines any manual overrides. The same doesn't happen for default overrides...

I'm not entirely sure, but I think that the bazel_dep is not used if you specify any explicit `go_deps.*_overrides`. If anything doesn't work with a `bazel_dep` with otherwise default settings,...

Without the explicit override envoy depends on `@xds` (the BCR module): ``` $ USE_BAZEL_VERSION=8.2.1 bazel query @xds//xds/annotations/v3:all @xds//xds/annotations/v3:pkg @xds//xds/annotations/v3:pkg_cc_proto @xds//xds/annotations/v3:pkg_cc_proto_cc_proto @xds//xds/annotations/v3:pkg_cc_proto_validate @xds//xds/annotations/v3:pkg_go_proto @xds//xds/annotations/v3:pkg_py_proto ``` With the explicit override envoy depends...

FYI @keith as you initially submitted xds to the BCR

> Also the go module is defined at the subfolder /go while the Bazel module uses the [root](https://github.com/bazelbuild/bazel-central-registry/blob/33e5f0088591a6a0a59ca2f8888ca44c217e8293/modules/xds/0.0.0-20240423-555b57e/source.json#L3) of the repository. So IIUC they are actually different modules. Okay, that...

Looks like that `pkg_go_proto` target is public, which means that they do need a non-development dependency on `gazelle` go_deps. Which means that we would need a way for a Bazel...

You should be able to use pregenerated proto files as long as you add the relevant Gazelle directive (such as `proto disable`) to the top-level BUILD file so that the...

Is it possible that `//:WORKSPACE` is the output of `print(ctx.attr.config)`, not `print(str(ctx.attr.config))`? The latter should never emit `//:WORKSPACE` on Bazel 6 or later - it should either print `@//:WORKSPACE` with...

I haven't found the issue yet. We have dropped support for Bazel 5 though, so we could just use canonical repo names with an `@@` prefix instead of deriving the...