bazelbuild/bazel

`bazel vendor` does not work as expected when using local registry.

Open

#25,503 opened on Mar 7, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (25,384 stars) (4,465 forks)batch import
P2help wantedteam-ExternalDepstype: bug

Description

Description of the bug:

The marker file for repos with patches will have different digest if repo is located at different places.

Likely because of https://github.com/bazelbuild/bazel/blob/f805f55e929069a00b83bf2de41fe945f1cb18d2/src/main/java/com/google/devtools/build/lib/packages/RuleFormatter.java#L64

Similar to https://github.com/bazelbuild/bazel/issues/19621

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

git clone https://github.com/boleynsu-org/monorepo A
git clone https://github.com/boleynsu-org/monorepo B
(cd A; bazel vendor //... --vendor_dir=v; cat $(ls v/*.marker | sort) >m)
(cd B; bazel vendor //... --vendor_dir=v; cat $(ls v/*.marker | sort) >m)
diff A/m B/m

Which operating system are you running Bazel on?

Fedora 41

What is the output of bazel info release?

release 8.1.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Contributor guide

Tech stack
java
Domain
build system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic understanding of BazelJava programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The bug is in the marker file generation for repos with patches. Likely the issue is in RuleFormatter.java at line 64 (https://github.com/bazelbuild/bazel/blob/f805f55e929069a00b83bf2de41fe945f1cb18d2/src/main/java/com/google/devtools/build/lib/packages/RuleFormatter.java#L64). The marker file digest differs based on the local path of the repo. Investigate how the digest is computed and why it includes the absolute path. Look at the related issue #19621 for context. The fix likely requires normalizing the path or excluding it from the digest computation.