bazel-contrib / bazel-contrib/rules_go
`nogo`: Issue with `isolated` extension and separate `go.mod` with `tools.go`
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 760
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 12
Description
When using a `tools.go` approach and having a separate `go.mod` with a separate `go_deps` usage via `--experimental_isolated_extension_usages` as documented at: https://github.com/bazel-contrib/rules_go/blob/v0.53.0/docs/go/core/bzlmod.md#depending-on-tools, my project fails.
I intend to add more details to this issue but for now I have a reproducible: https://github.com/albertocavalcante/tools-nogo-issue
And these are the error messages: https://github.com/albertocavalcante/tools-nogo-issue/blob/main/STDERR.md
Contributor guide
Research direction
Start with the documented “Depending on tools” section in docs/go/core/bzlmod.md, then reproduce the failure using the linked tools-nogo-issue project. Compare its separate go.mod, tools.go, and go_deps setup with STDERR.md while using --experimental_isolated_extension_usages. Done means the documented setup no longer produces the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100