Skip to content

Handle invalid UTF-8 as an OSC parse error - #202

Open
civilwarinfrance wants to merge 1 commit into
attwad:mainfrom
civilwarinfrance:fix/invalid-utf8-strings
Open

civilwarinfrance wants to merge 1 commit into
attwad:mainfrom
civilwarinfrance:fix/invalid-utf8-strings

Conversation

@civilwarinfrance

Copy link
Copy Markdown
Contributor

Malformed UTF-8 in an OSC address, type tag or string argument currently raises UnicodeDecodeError. This escapes the parse-error handling in the dispatcher instead of discarding the packet.

Convert decoding errors to the existing osc_types.ParseError. Tests cover malformed byte sequences, valid Unicode with a nonzero offset, and discarding malformed packets before successfully dispatching a valid one.

Validation: 195 tests pass; Ruff lint/format, mypy and package build pass locally. The new regression cases fail on the original code. Hosted CI is pending.

AI assistance: OpenAI Codex wrote and tested this patch.

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.

1 participant