-
Notifications
You must be signed in to change notification settings - Fork 793
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
Ref. 7290 propagate errors on take_next_data [7292] #962
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
IkerLuengo
force-pushed
the
bug/propagate_errors_to_client
branch
from
January 20, 2020 07:25
f866f1c
to
1bab813
Compare
EduPonz
reviewed
Jan 22, 2020
EduPonz
previously approved these changes
Jan 22, 2020
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.
LGTM
SubscriberHistory::deserialize_change must return the result of the deserialization and SubscriberHistory::takeNextData should propagate errors on deserialization and removal from history
IkerLuengo
force-pushed
the
bug/propagate_errors_to_client
branch
from
January 22, 2020 14:56
aac0f97
to
8c01f53
Compare
MiguelCompany
approved these changes
Jan 23, 2020
EduPonz
approved these changes
Jan 23, 2020
IkerLuengo
added a commit
that referenced
this pull request
Feb 21, 2020
This is a port of #962 from 1.9.x SubscriberHistory::deserialize_change must return the result of the deserialization and SubscriberHistory::takeNextData should propagate errors on deserialization and removal from history
MiguelCompany
pushed a commit
that referenced
this pull request
Feb 21, 2020
This is a port of #962 from 1.9.x SubscriberHistory::deserialize_change must return the result of the deserialization and SubscriberHistory::takeNextData should propagate errors on deserialization and removal from history
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SubscriberHistory::deserialize_change must return the result of the deserialization
and SubscriberHistory::takeNextData should propagate errors on deserialization and removal from history