You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: /home/runner/.cache/bazel/_bazel_runner/5c738117ebb090237e98e16aae223a35/external/build_stack_rules_proto/rules/private/proto_repository_tools_srcs.bzl:666:15: syntax error at 'newline': expected ]
It is unfortunately not easily reproduced. It often happens after a Bazel version upgrade. Once the repository gets in this state, only a bazel clean --expunge will let it recover. Interestingly, when you open that file, it is completely valid Starlark and the array is closed properly.
The text was updated successfully, but these errors were encountered:
There is a difference between rules_proto and gazelle here. Gazelle is only checking to see if this list is up to date and rules_proto seems to be trying to generate the file in the action. Could it be that writing to the file while building is somehow corrupting?
I was able to get this fixed for us by commented out L62-77 in a patch. Possible theory here is that updating this file while building causes a corruption and it gets cached remotely which is why it is non-deterministic.
We occasionally run into the following issue:
It is unfortunately not easily reproduced. It often happens after a Bazel version upgrade. Once the repository gets in this state, only a
bazel clean --expunge
will let it recover. Interestingly, when you open that file, it is completely valid Starlark and the array is closed properly.The text was updated successfully, but these errors were encountered: