Description
The CLI can crash on Windows PowerShell when terminal output contains non-ASCII characters.
This was found while running:
uv run osmsg --last day --format psql --psql-dsn $env:DATABASE_URL --name api_last_day
The first crash happened while printing the Unicode arrow →:
UnicodeEncodeError: 'charmap' codec can't encode character '\u2192'
After replacing that symbol locally, the CLI later crashed again while rendering the Rich output table. So this is likely not limited to hardcoded symbols. It may also happen with OSM usernames or metadata containing characters from Spanish, Nepali, Chinese, Turkish, etc.
Expected Behavior
The CLI should not crash when output contains non-ASCII text. It should either print Unicode correctly or safely replace unsupported characters.
Description
The CLI can crash on Windows PowerShell when terminal output contains non-ASCII characters.
This was found while running:
The first crash happened while printing the Unicode arrow →:
After replacing that symbol locally, the CLI later crashed again while rendering the Rich output table. So this is likely not limited to hardcoded symbols. It may also happen with OSM usernames or metadata containing characters from Spanish, Nepali, Chinese, Turkish, etc.
Expected Behavior
The CLI should not crash when output contains non-ASCII text. It should either print Unicode correctly or safely replace unsupported characters.