Skip to content

feat: support for remote.execution and remote.logging apis#958

Merged
thesayyn merged 2 commits intomainfrom
proto-client-changes
Mar 10, 2026
Merged

feat: support for remote.execution and remote.logging apis#958
thesayyn merged 2 commits intomainfrom
proto-client-changes

Conversation

@thesayyn
Copy link
Member

Changes are visible to end-users: yes

  • Searched for relevant documentation and updated as needed: yes
  • Breaking change (forces users to change their own code or config): no
  • Suggested release notes appear below: yes

Support for experimental remote.execution and remote.logging apis.

Test plan

  • New test cases added

@thesayyn thesayyn changed the title Proto client changes feat: support for remote.execution and remote.logging apis Mar 10, 2026
@thesayyn thesayyn force-pushed the proto-client-changes branch from 27db6a7 to 03e6a0d Compare March 10, 2026 19:20
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 27db6a746d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +1465 to +1467
Err(e) => {
*stream_opt = None;
panic!("stream error: {}", e);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Return stream errors instead of panicking in iterator

In the streaming branch generated by try_service, the iterator path used by for ... in stream panics when stream.message() returns an error. Any transient gRPC failure (for example cancellation or connection loss) during remote execution/logging iteration will terminate the whole process instead of producing a recoverable Starlark error or clean stream end, which is a production-facing reliability regression.

Useful? React with 👍 / 👎.

elif path.startswith("%workspace%"):
path = _resolve_import_path(path, workspace_dir, "")

result = parse_file(path, workspace_dir = workspace_dir, std = std)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Surface parse errors from bazelrc()

bazelrc() calls parse_file() and then immediately returns flags without checking result["errors"]. Because parse_file() encodes missing files/import failures/circular imports in that error list, callers currently get empty or partial flags silently instead of a failure, which can quietly misconfigure build/remote settings and is hard to debug.

Useful? React with 👍 / 👎.

@thesayyn thesayyn force-pushed the proto-client-changes branch from 03e6a0d to 053bda8 Compare March 10, 2026 19:47
@thesayyn thesayyn merged commit 60e34cd into main Mar 10, 2026
4 checks passed
@thesayyn thesayyn deleted the proto-client-changes branch March 10, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant