Big pack of files that cause problems

[qarmin]

Here I will public packs of broken files(mostly autofix bugs), that I found when fuzzing project.
I know that such issues should be created in separate issues, but I don't really have time to do this(there is ~700 broken files, which most probably have same source of problems), so feel free to do report it if you want.

I will try to provide new pack of broken files for each release

Command which I used

ruff . --fix --config ruff.conf

ruff.conf (please comment, if there is better way to test even more rules, or get better coverage of project)

select = ["ALL"]
exclude = []

A lot of files is minimized, so I suggest to check first the smallest files(a lot of files have less than 1KB ).
0.0.259 - 713 files - 1bac206 - Broken_259_713.zip
0.0.260 - 962 files - a142d71 - Broken_260_962.zip
0.0.261 - 767 files - cae5503 - Broken_261_767.zip
0.0.262 - 1384 files - 6e8d561 - Broken_262_1384.zip
0.0.263 - 3678 files - 3c9f5e2 - Broken_263_3678.zip
0.0.265 - 5417 files - 11e1380 - Broken_265_5417.zip
0.0.285 - 374 files - ea72d5f - Broken_285_374.zip

[charliermarsh]

Thank you! This is great, no need to file separate issues.

[jfmengels]

@qarmin can I ask how you generated these fuzzed files? I'd be interested for doing the same for my own linter (elm-review, for Elm).

[charliermarsh]

@jfmengels -- I believe it was done with cargo-fuzz, see #3507.

[qarmin]

https://crates.io/crates/create_broken_files - tool to create broken files

https://github.com/qarmin/Automated-Fuzzer - wrapper on this tool, that automates creating and checking broken files

I used before cargo fuzz, but I was only able to find only one bug with it - #3336, all others bug reports comes from this tools

[charliermarsh]

We love broken files

[qarmin]

Closing since I managed to report them one by one without too much duplicates