Explain why a module hasn't been found in any registry #24804
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build.
github-actions
bot
added
team-ExternalDeps
Collaborator
Author
|
@bazel-io fork 7.5.0 |
Collaborator
Author
|
@bazel-io fork 8.1.0 |
This was referenced Dec 28, 2024
meteorcloudy
reviewed
Jan 2, 2025
src/main/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistry.java
Outdated
Show resolved
Hide resolved
meteorcloudy
added
awaiting-PR-merge
github-actions
bot
removed
the
awaiting-PR-merge
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Jan 8, 2025
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build. Fixes bazelbuild#24803 Closes bazelbuild#24804. PiperOrigin-RevId: 713142592 Change-Id: Id541f5710481bd947c09d8dba315d683a1666b1c
fmeum
added a commit
to fmeum/bazel
that referenced
this pull request
Jan 9, 2025
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build. Fixes bazelbuild#24803 Closes bazelbuild#24804. PiperOrigin-RevId: 713142592 Change-Id: Id541f5710481bd947c09d8dba315d683a1666b1c (cherry picked from commit 6061e5e)
meteorcloudy
pushed a commit
that referenced
this pull request
Jan 13, 2025
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build. Fixes #24803 Closes #24804. PiperOrigin-RevId: 713142592 Change-Id: Id541f5710481bd947c09d8dba315d683a1666b1c (cherry picked from commit 6061e5e) Fixes #24805
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 20, 2025
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build. Fixes #24803 Closes #24804. PiperOrigin-RevId: 713142592 Change-Id: Id541f5710481bd947c09d8dba315d683a1666b1c Commit 6061e5e Co-authored-by: Fabian Meumertzheim <[email protected]> Co-authored-by: Ian (Hee) Cha <[email protected]>
fmeum
added a commit
to fmeum/bazel
that referenced
this pull request
Jan 29, 2025
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build. Fixes bazelbuild#24803 Closes bazelbuild#24804. PiperOrigin-RevId: 713142592 Change-Id: Id541f5710481bd947c09d8dba315d683a1666b1c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes it easier for users to discover that a module hasn't been found because its absence was recorded in the lockfile during a previous build.
Fixes #24803