-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
local_path_override doesn't get invalidated for MODULE.bazel file creation #22687
Labels
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Comments
github-actions
bot
added
the
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
label
Jun 11, 2024
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Jun 11, 2024
Fixes bazelbuild#22687 Closes bazelbuild#22700. PiperOrigin-RevId: 642340825 Change-Id: I96f496b309c4740ae561f69098eca54a12a574f0
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Jun 11, 2024
Fixes bazelbuild#22687 Closes bazelbuild#22700. PiperOrigin-RevId: 642340825 Change-Id: I96f496b309c4740ae561f69098eca54a12a574f0
A fix for this issue has been included in Bazel 7.3.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Description of the bug:
If you set a local_path_override to a directory which doesn't contain a MODULE.bazel, then create one, a subsequent build will continue to complain that the file didn't exist.
Which category does this issue belong to?
External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
The
query
before theshutdown
should have worked because the situation on disk was resolved and the repository fetch should have been invalidated by the filesystem changes.Note that sometimes the first query only prints the second error not the first - when that happens, the first query after creating the MODULE.bazel file will work.
Which operating system are you running Bazel on?
macOS
What is the output of
bazel info release
?release 7.2.0
If
bazel info release
returnsdevelopment 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
?No response
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
The text was updated successfully, but these errors were encountered: