Skip to content

errors: handle ParseError and generic exceptions in FormatErrorMsg - #1333

Open
Fire162 wants to merge 1 commit into
google:mainfrom
Fire162:fix/format-error-msg-robustness
Open

Fire162 wants to merge 1 commit into
google:mainfrom
Fire162:fix/format-error-msg-robustness

Conversation

@Fire162

@Fire162 Fire162 commented Oct 26, 2026

Copy link
Copy Markdown

Handle ParseError and generic exceptions gracefully in FormatErrorMsg instead of failing with indexing errors when accessing args[1]. Also fallback safely to error messages and filename attributes for non-syntax exceptions.

Fixes #1304
Fixes #1286

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: ParseError when using dictionary in logging.getLogger omitting [style] breaks yapf

1 participant