Repository navigation
fix: pass --lockfile_mode=off to internal bazel info probes - #1562
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
|
Aspect Workflows TasksTask Results
Install |
|
Generated by Claude Code |
We have a GH incident at the moment. I think it's related since I'm seeing several PRs failing CI checks. |
|
Update on the So this looks like Generated by Claude Code |
7f16872 to
8b3db86
Compare
Fixes #1561 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TwhYhtbtbN5H2FtZ9qUjpD
The aspect materializer's `bazel info install_base` probe was missed by the earlier change; give it the same flag so it cannot rewrite MODULE.bazel.lock either. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013uQ5fDkcwzTosokxPggJWk
9dadffe to
0f7ce7a
Compare
Adds
--lockfile_mode=offafterinfoin the internal probe commands (check_bazel_server,get_output_base,server_info_with_startup_flags,client_pid,is_server_busy,server_pid_nonblocking) so a reused Bazel 8 server can't rewriteMODULE.bazel.lock.Fixes #1561
🤖 Generated with Claude Code
https://claude.ai/code/session_01TwhYhtbtbN5H2FtZ9qUjpD
Generated by Claude Code