Updated Fuzzer harness to address all dialects#2203
Merged
iffyio merged 1 commit intoapache:mainfrom Feb 10, 2026
Merged
Conversation
Contributor
|
Looks good to me but I do not have merge rights - @iffyio it is a pretty small PR if you can check it out when you have time. |
iffyio
approved these changes
Feb 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fuzzer harness was formerly only fuzzing
GenericDialectand none of the otherDialecttypes. I modified the harness to account for all dialects and it should now be fuzzing all dialects.