LucaCappelletti94 opened a new issue, #2519: URL: https://github.com/apache/datafusion-sqlparser-rs/issues/2519
I believe having continuous fuzzer will help us a lot in the process more effectively the increasing number of PR and avoid merging regressions, other than of course discover current errors. I propose the following sequence of PRs: 1. Switching from honggfuzz to cargo-fuzz/libFuzzer harness. I agree that in the past honggfuzz was the goto solution, and it was also my favourite, but cargo-fuzz has improved a lot in the last few years and is required by OSS-Fuzz and ClusterFuzzLite. 2. Adding a harness executing the parse -> `Display` -> re-parse loop, plus an actually committed seed corpus. 3. Fuzz-byte-driven weighted recursive query generator (SparkFuzz/SQLsmith style), sidestepping #2193's `Arbitrary` blocker which is still blocked to this day because of the ignored upstream PR https://github.com/akubera/bigdecimal-rs/pull/163 4. OSS-Fuzz application (`projects/datafusion-sqlparser-rs`) which I believe we may be approved for, given the reasonable user pool of this crate 5. ClusterFuzzLite PR gate + daily batch, same targets. @alamb @iffyio opinions? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
