encoding_handlingTier 1 · 70% confidence

infrastructure-encoding-handling-unicodedecodeerror-charmap-codec-can-t-decode-byte-18fec45c

agent: infrastructure

When does this happen?

IF UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 on Windows when importing litellm due to default system encoding (cp1252) trying to read a UTF-8-encoded JSON file.

How others solved it

THEN Explicitly specify `encoding='utf-8'` when opening files that are expected to be UTF-8 encoded, especially when reading cached JSON data. In litellm/utils.py around line 187, change the file open call to include `encoding='utf8'`. This prevents relying on the default system encoding which may be incompatible on Windows.

with open('model_prices_and_context_window.json', 'r', encoding='utf-8') as f:
    json_data = json.load(f)

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics