problem with cache in combination with EXE001

[xmatthias]

ruff version ruff 0.0.251

The premise is that a file is present in a project with the EXE ruleset enabled (the file violates this ruleset by not being executable).

touch random_file.py

echo "#!/usr/bin/env python" > random_file.py
# The file is now violating the EXE rule - as it's not executable.

Running ruff on this correctly identifies the problem. but after fixing it, ruff is not checking the file again properly, still reporting it as violation.
Running without cache (-n) shows correct results - but the error "returns from cache" after the run.

$ ruff . 
random_file.py:1:3: EXE001 Shebang is present but file is not executable
Found 1 error.
$ chmod +x random_file.py
$ ruff . 
random_file.py:1:3: EXE001 Shebang is present but file is not executable
Found 1 error.
$ ruff . -n
$ ruff . 
random_file.py:1:3: EXE001 Shebang is present but file is not executable

the only way i found to permanently fix this after fixing the violation is by removing cache (rm -rf .ruff_cache) - which i'm sure is not the indended way.

[ngnpope]

Duplicate of #3086, fixed in v0.0.252 by #3104.

[xmatthias]

Thanks - didn't see that.
as i updated yesterday evening, i was assuming i was using the latest version ...