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
[fuzzing] Fix fuzzer found bug #33291
Conversation
grpc_core::TraceFlagList::Set(strings[i] + 1, false); | ||
namespace { | ||
void ParseTracers(absl::string_view tracers) { | ||
for (auto s : absl::StrSplit(tracers, ',')) { |
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.
I think you can use the absl::SkipWhitespace()
predicate in absl::StrSplit()
here, which will eliminate the need for the next two lines.
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.
I'll send a follow-up applying that a bit more widely!
We had an infinite recursion in our tracer parsing code... probably not a biggy, but it was blocking the fuzzers so fixing. <!-- If you know who should review your pull request, please assign it to that person, otherwise the pull request would get assigned randomly. If your pull request is for a specific language, please add the appropriate lang label. -->
We had an infinite recursion in our tracer parsing code... probably not a biggy, but it was blocking the fuzzers so fixing. <!-- If you know who should review your pull request, please assign it to that person, otherwise the pull request would get assigned randomly. If your pull request is for a specific language, please add the appropriate lang label. -->
We had an infinite recursion in our tracer parsing code... probably not a biggy, but it was blocking the fuzzers so fixing.