ObjectRequestMessage for async example#2948
Merged
LaRiffle merged 1 commit intoOpenMined:masterfrom Jan 22, 2020
Merged
Conversation
LaRiffle
approved these changes
Jan 22, 2020
Contributor
LaRiffle
left a comment
LaRiffle
left a comment
There was a problem hiding this comment.
Nice catch thanks!
(correct usage indeed can be found in base.py line 623 obj = self.send_msg(ObjectRequestMessage((obj_id, user, reason)), location))
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The MNIST async websocket exampe fails because the workers cannot unpack an int. The message sent needs to be the tuple defined previously.