| SLSA-Policy-Verified | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| SLSA-Policy-Verified | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| SLSA-Policy-Verified | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| SLSA-Policy-Verified | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| SLSA-Policy-Verified | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
third_party/grpc/src/**/*.pykeep in alphabetical order
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| SLSA-Policy-Verified | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Resolving comments.
Gemini says: Done! I have updated the `.yapfignore` file to keep the entries in alphabetical order.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Is this safe in terms of compatibility between Chromium gRPC version and other builders? gRPC has a history of breaking changes, I just want to be sure this won't become a maintenance burden for us. Are changes being made elsewhere to ensure things stay in sync?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Is this safe in terms of compatibility between Chromium gRPC version and other builders? gRPC has a history of breaking changes, I just want to be sure this won't become a maintenance burden for us. Are changes being made elsewhere to ensure things stay in sync?
From what I can tell, at least for the mediashell case, it should be fine. The chromium code and the cast_service code are in different libraries and only communicate "over the wire" across process boundaries, so there's no ABI or ODR issue. My understanding is that the linux builds also use separate binaries for the core process and the runtime so the same logic should apply there too. However, my LLM Extension agent found that iOS uses it too and cites crbug.com/40062500, but it looks like that wasn't about compatibility, but rather staying on top of CVEs, which is exactly what Crobar is meant to fix.
'source',this should be updated too, right?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
To Gemini: some linux presubmits are failing, please make sure that the GRPC code builds before uploading a new PS
Gemini says: Addressed all reviewer comments, rebased on main, verified that the entire gRPC code and cast_shell target compiles cleanly with 0 errors, and triggered CQ Dry Run!
| Commit-Queue | +1 |
Gemini says: Addressed. Automated Crowbar updates will target third_party/grpc/src/ where all chromium-specific configurations remain stable. Verified that the rebased CL compiles cleanly under //third_party/grpc:grpc++ with 0 errors.
Gemini says: Resolved. Rebased cleanly on main, ran gclient sync -D to align dependencies, and verified that local compilation compiles successfully!
Gemini says: Resolved. Sorted the entry alphabetically under the third-party section.
Gemini says: Resolved. Updated the skip_child_includes entry to src.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |