Skip to content

Conversation

@aslonnie
Copy link
Collaborator

carrying on @mattip 's work

mattip and others added 30 commits July 25, 2025 16:49
This reverts commit 8501079.

Signed-off-by: mattip <[email protected]>
Signed-off-by: Matti Picus <[email protected]>
Signed-off-by: Matti Picus <[email protected]>
Signed-off-by: Matti Picus <[email protected]>
@aslonnie aslonnie requested a review from a team as a code owner November 15, 2025 15:53
@aslonnie aslonnie added the go add ONLY when ready to merge, run all tests label Nov 15, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates several core dependencies: protobuf to 28.2, absl to 20240722, and gRPC to 1.67.1. The changes include updating dependency definitions in Bazel files, adapting C++ code to new Protobuf APIs, and adjusting patches for the new dependency versions. The CI configuration is also updated to use larger instances, likely to handle increased resource usage. Overall, the changes look correct and necessary for the dependency upgrades. I have one suggestion regarding a now-empty patch file that is still being applied.

patches = [
"@io_ray//thirdparty/patches:grpc-cython-copts.patch",
"@io_ray//thirdparty/patches:grpc-avoid-goaway-messages.patch",
"@io_ray//thirdparty/patches:grpc-zlib-fdopen.patch",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The patch file grpc-zlib-fdopen.patch has been emptied in this pull request, but it's still listed here to be applied to com_github_grpc_grpc. While applying an empty patch might be a no-op, it's confusing and can hide intent. If this patch is no longer necessary with the updated gRPC version, it would be clearer to remove this line entirely.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Bug: Stale Patch Reference Blocks Builds

The patch file grpc-zlib-fdopen.patch has been completely emptied but is still referenced in bazel/ray_deps_setup.bzl at line 282. Applying an empty patch file will cause Bazel build failures when processing the grpc dependency.

thirdparty/patches/grpc-zlib-fdopen.patch#L1-L1

https://github.com/ray-project/ray/blob/b27b2b65c4924bf4081b76004be94be0987ea375/thirdparty/patches/grpc-zlib-fdopen.patch#L1

Fix in Cursor Fix in Web


build:linux --cxxopt="-std=c++17"
build:macos --cxxopt="-std=c++17"
build:clang-cl --cxxopt="-std=c++17"
build:clang-cl --cxxopt="-std:c++17"
Copy link

Choose a reason for hiding this comment

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

Bug: Clang-cl Standard Flag Syntax Mix-up

The C++ standard flag for clang-cl was changed from -std=c++17 to -std:c++17, mixing GCC-style prefix (-) with MSVC-style separator (:). The correct syntax is either -std=c++17 (GCC-style with equals) or /std:c++17 (MSVC-style with slash and colon). This invalid flag syntax will cause compilation failures when using the clang-cl configuration.

Fix in Cursor Fix in Web

@ray-gardener ray-gardener bot added the core Issues that should be addressed in Ray Core label Nov 15, 2025
@aslonnie aslonnie marked this pull request as draft November 15, 2025 20:50
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had
any activity for 14 days. It will be closed in another 14 days if no further activity occurs.
Thank you for your contributions.

You can always ask for help on our discussion forum or Ray's public slack channel.

If you'd like to keep this open, just leave any comment, and the stale label will be removed.

@github-actions github-actions bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Nov 30, 2025
@aslonnie aslonnie removed the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Dec 1, 2025
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had
any activity for 14 days. It will be closed in another 14 days if no further activity occurs.
Thank you for your contributions.

You can always ask for help on our discussion forum or Ray's public slack channel.

If you'd like to keep this open, just leave any comment, and the stale label will be removed.

@github-actions github-actions bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Dec 16, 2025
@aslonnie aslonnie removed the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Dec 16, 2025
@aslonnie
Copy link
Collaborator Author

@aslonnie
Copy link
Collaborator Author

cc @andrew-anyscale too

@aslonnie
Copy link
Collaborator Author

upgrading the libraries also upgrades rules_python, and macos and windows CI starts failing now.

@aslonnie
Copy link
Collaborator Author

aslonnie commented Jan 6, 2026

I need to remove the pygithub package (or the test db altogether) so that the python rules thing can be upgraded without breaking macos and windows test jobs..

or maybe via some other means, like further upgrade or patch python rules and its related dependencies... ugh.. bazel...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issues that should be addressed in Ray Core go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants