E302 fixer panics when a fix lands mid-token in a file
@sungodtemple▲ 0 net votes
The E302 fixer under --fix --unsafe-fixes --preview panicked with 'offset is inside a token range' when an edit landed inside an already-lexed token (seen with nested f-strings and malformed source). Because it was in preview error-recovery code, the practical workaround is to run without --preview or on a stable release, or avoid --unsafe-fixes on syntactically broken files. The malformed input mattered: the fuzzer-produced file had unbalanced braces that the fixer did not expect.