-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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][Protobuf] loose upper bound for protobuf #29224
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scv119
added
the
@author-action-required
The PR author is responsible for the next step. Remove tag to send back to the reviewer.
label
Oct 11, 2022
jjyao
approved these changes
Oct 12, 2022
rkooo567
approved these changes
Oct 13, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can we test this btw?
is there a test case that broke before? |
scv119
added
tests-ok
The tagger certifies test failures are unrelated and assumes personal liability.
and removed
@author-action-required
The PR author is responsible for the next step. Remove tag to send back to the reviewer.
labels
Oct 17, 2022
@rkooo567 we have test_latest_core_dependencies which test the latest protobuf is compatible with ray. |
richardliaw
approved these changes
Oct 17, 2022
scv119
added a commit
to scv119/ray
that referenced
this pull request
Oct 17, 2022
This upper bound was introduced in ray-project#25211 but the root cause is supposed be fixed by ray-project#25648.
rickyyx
pushed a commit
that referenced
this pull request
Oct 17, 2022
7 tasks
krfricke
added a commit
that referenced
this pull request
Oct 24, 2022
#29224 removed the protobuf upper bound but #29375 was oroginally created on an older requirements file and accidentally reverted the update for unix builds. Signed-off-by: Kai Fricke <[email protected]>
WeichenXu123
pushed a commit
to WeichenXu123/ray
that referenced
this pull request
Dec 19, 2022
This upper bound was introduced in ray-project#25211 but the root cause is supposed be fixed by ray-project#25648. Signed-off-by: Weichen Xu <[email protected]>
WeichenXu123
pushed a commit
to WeichenXu123/ray
that referenced
this pull request
Dec 19, 2022
ray-project#29224 removed the protobuf upper bound but ray-project#29375 was oroginally created on an older requirements file and accidentally reverted the update for unix builds. Signed-off-by: Kai Fricke <[email protected]> Signed-off-by: Weichen Xu <[email protected]>
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
tests-ok
The tagger certifies test failures are unrelated and assumes personal liability.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
This upper bound was introduced in #25211 but the root cause is supposed be fixed by #25648.
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.