You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
ClusterFuzzLite PR gate + daily batch, same targets.
Adding a harness executing the parse -> Display -> re-parse loop, plus an actually committed seed corpus.
OSS-Fuzz application (projects/datafusion-sqlparser-rs) which I believe we may be approved for, given the reasonable user pool of this crate
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:
Display-> re-parse loop, plus an actually committed seed corpus.projects/datafusion-sqlparser-rs) which I believe we may be approved for, given the reasonable user pool of this crateArbitraryblocker which is still blocked to this day because of the ignored upstream PR Added support for Arbitrary akubera/bigdecimal-rs#163@alamb @iffyio opinions?
EDIT: swapped order of steps as mentioned in #2519 (comment)