Protobuf can go back to protobuf>=3.12.2
#638
Closed
+824
−3
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.
Make sure to delete everything but:
requirements.txt
, there are other updates toRoutingTable.py
to allow for updating timestamps tonode_ids
in the routing table for applications like Petals to use... Or even just make another commitWith
protobuf>=3.12.2,<5.28.0
I receive the error:This should happen if you
--force
a pip install again and try to start a server in Petals.This was fixed here: protocolbuffers/protobuf#18096 (It looks like)
Switching back to
protobuf>=3.12.2
resolves this issue on Linux and WSL for me