-
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 on tilde separators in cache #23322
Comments
Thanks for the report! This is pretty bad, but I think it should be fine for people on 7.3.1 as The immediate fix is to run |
|
Wait, that's surprising. Do you get the exact same error message? I don't understand how that's possible, then. |
@Wyverald My apologies-- i'm not sure what I did before when I tested. I must've early-aborted the expunge or something. I tried again just now, and building after |
Especially due to bazelbuild#23127, older marker files may contain entries that don't even parse correctly. Instead of crashing Bazel, we should signal a refetch. Fixes bazelbuild#23322. Closes bazelbuild#23336. PiperOrigin-RevId: 666416942 Change-Id: Ie5507654f69825d93f9523d9c209d417fb3cdaf6
Especially due to bazelbuild#23127, older marker files may contain entries that don't even parse correctly. Instead of crashing Bazel, we should signal a refetch. Fixes bazelbuild#23322. Closes bazelbuild#23336. PiperOrigin-RevId: 666416942 Change-Id: Ie5507654f69825d93f9523d9c209d417fb3cdaf6
Bazel 7.1.0 and 7.2.0 contains a bug where + characters in labels in the repository marker files cannot be parsed. Improves bazelbuild#23336 that fixed bazelbuild#23322.
Bazel 7.1.0 and 7.2.0 contains a bug where + characters in labels in the repository marker files cannot be parsed. This was fixed in commit d62e0a0. To reduce the rusk of future bugs in the same area, this change skips parsing the file if the first line shows that the content will not be used anyway, which should be reasonably safe if introducing new formats. Improves bazelbuild#23336 that fixed bazelbuild#23322.
Bazel 7.1.0 and 7.2.0 contains a bug where + characters in labels in the repository marker files cannot be parsed. This was fixed in commit d62e0a0. To reduce the rusk of future bugs in the same area, this change skips parsing the file if the first line shows that the content will not be used anyway, which should be reasonably safe if introducing new formats. Improves #23336 that fixed #23322. Closes #23642. PiperOrigin-RevId: 679330823 Change-Id: I8123bdde047735ced3eabed3df68112d44318b08
Bazel 7.1.0 and 7.2.0 contains a bug where + characters in labels in the repository marker files cannot be parsed. This was fixed in commit d62e0a0. To reduce the rusk of future bugs in the same area, this change skips parsing the file if the first line shows that the content will not be used anyway, which should be reasonably safe if introducing new formats. Improves #23336 that fixed #23322. Closes #23642. PiperOrigin-RevId: 679330823 Change-Id: I8123bdde047735ced3eabed3df68112d44318b08
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:
When attempting to update Pigweed from
8.0.0-pre.20240618.2
to8.0.0-pre.20240812.1
we hit the following error when building any target (e.g.bazelisk build //pw_chrono:system_clock
):A bisect points at #23103. It seems like there was an intentional choice to change the separator. Deleting
MODULE.bazel.lock
does not solve the issue,nor does.bazelisk clean --expunge
Which category does this issue belong to?
Core
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Clone https://pigweed.googlesource.com/pigweed/pigweed/
Update
.bazelversion
to8.0.0-pre.20240812.1
bazelisk build //pw_chrono:system_clock
(or any other target)The text was updated successfully, but these errors were encountered: