Skip to content
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

fix: ignore non-nil but empty error strings in Describe/Alter client quotas responses #2096

Merged
merged 2 commits into from
Jan 4, 2022

Conversation

agriffaut
Copy link
Contributor

That PR resolve issue #2095, it has been tested against Kafka 2.7.0 and Kafka 2.8.1

@agriffaut agriffaut requested a review from bai as a code owner December 29, 2021 17:14
@dnwe
Copy link
Collaborator

dnwe commented Dec 29, 2021

Interesting. We should check the broker source to see when/why this changed. This also suggests we need DescribeClientQuotas coverage in the functional_test suite too

@agriffaut agriffaut force-pushed the bug/issue-2095 branch 2 times, most recently from 83271fc to 581f074 Compare December 30, 2021 10:13
@agriffaut
Copy link
Contributor Author

Hi @dnwe i added some integration tests which covers describe / alter / delete of client quotas, thanks for your feedbacks !

@dnwe dnwe changed the title bug #2095 - verify empty error string even if it is a nullable string fix: ignore non-nil but empty error strings in Describe/Alter client quotas responses Jan 4, 2022
@dnwe
Copy link
Collaborator

dnwe commented Jan 4, 2022

@agriffaut fantastic! thank you for doing that, changes and tests LGTM — approving and merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants