-
Notifications
You must be signed in to change notification settings - Fork 24
Fix the publish error response #220
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
Conversation
Golang moved the project to Uber: https://github.com/uber-go/mock Signed-off-by: Aitor Pérez Cedres <acedres@vmware.com>
Publish error frame returns a list of publishing errors. The caller has to go through all the errors to determine what publishing IDs failed to publish. We were not reading all the bytes from the socket, which was missaligning the buffer, leading to a panic in the handleIncoming function. Signed-off-by: Aitor Pérez Cedres <acedres@vmware.com>
183902b
to
f5e9eea
Compare
|
Ok I understood the problem, we filter the flaky tests: Let's ignore it for this PR. Maybe we should investigate how to remove the flaky filter in |
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.
Looks good to me. Publish error is not tested in the e2e
test btw
We could add an e2e test to trigger all possible errors from the broker 🤔 I'll create an issue for that |
Summary