-
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
Crash in vendor subcommand #23521
Comments
This looks very weird, do you actually have a repo called |
No, unless one of our transitive dependencies has one (that'd be weird though).
Not anytime soon, but if you're fine with waiting then I'll get back to you eventually. |
After running |
The crash loop does not get resolved by I can reproduce it by running
|
Duplicates #22740 |
#23771 should help avoid this. A temporary solution is to add the vendor dir into |
- Adding `--vendor_dir` to ignored package prefixes as if it's added in the `.bazelignore` file. - This allows users to do `bazel build //...` after vendoring external deps in the source root without manually adding the vendor dir in `.bazelignore`. Fixes bazelbuild#23521 Closes bazelbuild#23771. PiperOrigin-RevId: 680994986 Change-Id: I9c8b76ca20b9060232dfe05460a8fc857c92e93f
- Adding `--vendor_dir` to ignored package prefixes as if it's added in the `.bazelignore` file. - This allows users to do `bazel build //...` after vendoring external deps in the source root without manually adding the vendor dir in `.bazelignore`. Fixes #23521 Closes #23771. PiperOrigin-RevId: 680994986 Change-Id: I9c8b76ca20b9060232dfe05460a8fc857c92e93f Backporting d42301b
A fix for this issue has been included in Bazel 7.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Description of the bug:
Presumably some symlink or something in our source root messes up the vendor subcommand - it shouldn't crash with an exception though.
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.
No response
Which operating system are you running Bazel on?
MacOS
What is the output of
bazel info release
?development
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.5f5d70b via bazelisk (it's a commit from the 7.4.0 branch)
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: