Support Bazel repository contents cache
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- build-system
Research direction
Start with handler/getchangedtargets.go and trace how target graph computation finds Bazel repository metadata, especially the expected external/<repo>.marker file. Compare that lookup with the repository contents cache layout described in the issue, where metadata is in a .recorded_inputs file. Done when analysis handles this layout without the reported missing-marker error; run the relevant target graph tests.
Written by the indexing model from the issue text.
Description
I am trying to setup Tango for one of our projects as a POC. The project is a Java service built with Bazel 9.3.0.
I am facing the following issue when analyzing the repository:
2026-10-20T12:03:08.957+0200 ERROR handler/getchangedtargets.go:39 GetChangedTargets failed {"repository": "demand-api", "error": "fetch target graphs: failed to get target graph #1: get target graph: compute target graph: bzlmod repo \"rules_jvm_external++maven+io_netty_netty_codec_protobuf_4_2_19_Final\" has targets in query but no marker file", "error_code": "infra"}
AI assisted analysis: Bazel successfully finds the dependency but Tango fails afterward while calculating target hashes. Tango uses Bazel's repository metadata to detect changes to external dependencies. It currently expects that metadata in an external/@<repo>.marker file. With Bazel's repository contents cache, the dependency directory can instead be a symlink into a shared cache, with metadata stored alongside the cached directory in a .recorded_inputs file. This layout was observed in the affected Tango workers. Tango only looks for .marker files, so it treats the dependency's metadata as missing and aborts the request.
Perhaps I am missing some necessary configuration in the project's .bazelrc to support Tango. Do you any have suggestions or workarounds?
- Dominant language
- Go
- Stars
- 23
- Forks
- 12
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uber/tango
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
race in core/bazelMay be free again @sywhang claimed this 136 days ago, and no pull request is open. Open
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
kubescape/node-agent#1099 ·
Maintainers usually reply within 1 day
-
import-export
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
genealogix/glx#1498 ·
Maintainers usually reply within 2 days
-
Docs: 2 broken linksOpenBug pulumi/pulumi-terraform-bridge R2 S2
Difficulty 1/5 Under an hour Newbie friendliness 72/100
pulumi/pulumi-terraform-bridge#3713 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ossf/pvtr-github-repo-scanner#539 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
goreleaser/goreleaser#7316 ·
Maintainers usually reply within 1 day