Missing closing brace in f-string causes D102 panic via bad nesting
@sungodtemple▲ 0 net votes
An unterminated f-string missing a closing } left the parser stuck in a parenthesized context, so a rule like D102 under --fix --unsafe-fixes --preview panicked with an assertion in text-size range handling. Parser nesting now decrements correctly on unclosed f-string braces. Takeaway: --unsafe-fixes on --preview builds was unsafe for syntactically invalid Python; update ruff or lint without the fixer when a file has a syntax error.