-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Replicated Subscription fail with IllegalStateException #10097
Labels
type/bug
The PR fixed a bug or issue reported a bug
Comments
After fixing the exception in the description with #10098 changes, a new issue appears:
|
sijie
pushed a commit
that referenced
this issue
Apr 9, 2021
Fixes: #10097 ### Motivation See #10097 for the issue. It seems that the code broke when the switch was made to LightProto in #9046. ### Modifications It is necessary to use `msg.getMessageBuilder().hasReplicatedFrom()` and use logic that only calls `msg.getMessageBuilder().getReplicatedFrom()` if `hasReplicatedFrom()` returns true.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
This exception is repeated on the log when using replicated subscriptions:
To reproduce
It might be possible to reproduce the issue with fewer steps.
Observations
It seems that the code location broker after the switch to LightProto (#9046).
The fix is easy for the exception above. The concern is the lack of test coverage for replicated subscriptions.
The text was updated successfully, but these errors were encountered: