Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Core] Fix the accidental protobuf backward incompatible changes (#37… #37826

Merged
merged 1 commit into from
Jul 26, 2023

Conversation

architkulkarni
Copy link
Contributor

@architkulkarni architkulkarni commented Jul 26, 2023

…650)

Cherry pick of #37650 to the release branch.


Move the JobTableData to "backward compatibility required" section since it is. However, we should generally be careful when we modify the protobuf to keep the backward compatibility. https://github.com/ray-project/ray/pull/35188/files#diff-66e7c4b1cbb0a6ce505e17964332b0e4d26631f291bcbabd221d13fa09707d90 -> Fix the protobuf compatibility by keep the driver_ip_address and add a new field driver_address at the end of the protobuf Append fields instead of adding in the middle. To do this, we move the field is_running_tasks to the end. We also mark the old address field as deprecated in a comment.

The resulting protobuf is backwards compatible with Ray 2.5.1 and any prior version, and breaks compatibility with Ray 2.6.0 and Ray 2.6.1. It's not possible to be backwards compatible with both simultaneously.


Why are these changes needed?

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

…-project#37650)

Move the JobTableData to "backward compatibility required" section since it is. However, we should generally be careful when we modify the protobuf to keep the backward compatibility.
https://github.com/ray-project/ray/pull/35188/files#diff-66e7c4b1cbb0a6ce505e17964332b0e4d26631f291bcbabd221d13fa09707d90 -> Fix the protobuf compatibility by
keep the driver_ip_address and add a new field driver_address at the end of the protobuf
Append fields instead of adding in the middle. To do this, we move the field is_running_tasks to the end.
We also mark the old address field as deprecated in a comment.

The resulting protobuf is backwards compatible with Ray 2.5.1 and any prior version, and breaks compatibility with Ray 2.6.0 and Ray 2.6.1. It's not possible to be backwards compatible with both simultaneously.

---------

Signed-off-by: SangBin Cho <[email protected]>
Signed-off-by: Archit Kulkarni <[email protected]>
Co-authored-by: Archit Kulkarni <[email protected]>
@rickyyx rickyyx merged commit b03a76b into ray-project:releases/2.6.2 Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker P0 Issue that blocks the release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants