Vitess fuzzers are broken

[dbussink]

Currently the Vitess fuzzers are broken and have been for a while. There have been refactors on the Vitess end without realizing that they would affect things here.

I tried vitessio/vitess#17380, but it looks like there's copied set in this repository. I'm not sure how to test / fix that though.

@AdamKorcz Would you have any input / way to fix this here? Looks like you did most of the Vitess additions here?

[AdamKorcz]

Yes, I have been handling the Vitess fuzzers over several years. Ideally, they should live in the Vitess repository, such that changes to the Vitess source don't break the fuzz build. I will be happy to clean up all the fuzzers and migrate them upstream if you will accept the PRs.

[dbussink]

Yes, I have been handling the Vitess fuzzers over several years. Ideally, they should live in the Vitess repository, such that changes to the Vitess source don't break the fuzz build. I will be happy to clean up all the fuzzers and migrate them upstream if you will accept the PRs.

That sounds like a good idea then to keep them in Vitess so it's easier to maintain and avoid regressions here.

[Aaravanand00]

Hi @AdamKorcz @dbunsink,

I'm a new contributor interested in fuzzing. This migration
seems like a great case study for other CNCF projects.

Would it be valuable to document:

1. Why this migration is needed
2. Steps involved in moving fuzzers upstream
3. Best practices for future projects
4. Testing/validation checklist

I could create this documentation as you work through the
migration, if that would be helpful.

Let me know!