-
Notifications
You must be signed in to change notification settings - Fork 593
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
[v23.1.x] k/protocol: Checking for tag value to be 0 #11645
[v23.1.x] k/protocol: Checking for tag value to be 0 #11645
Conversation
Tag fields that are primitives should not be encoded if their value is equal to 0. Fixes: redpanda-data#11358 Signed-off-by: Michael Boquard <michael@redpanda.com> (cherry picked from commit 5991376)
We shouldn't crash if we parse an unknown error code. Signed-off-by: Michael Boquard <michael@redpanda.com> (cherry picked from commit 90de7ca)
@michael-redpanda This might happen quite a lot, I wonder if you should run the linter as part of backporting. |
The automated cherry-picking by the bot is probably always going to fail at this point (until we stop supporting builds that depend on clang14, which is going to be a while). |
Signed-off-by: Michael Boquard <michael@redpanda.com> (cherry picked from commit e77a935)
77e57d1
to
9ba3cee
Compare
Force push
|
Build failure waiting on #11690 |
I couldn't tell if you restarted the build, so I clicked retry button @michael-redpanda |
Rerunning CI now that #11712 has merged and fixed the unit test bug |
Backport of PR #11443
Fixes #11643,