Jeroen UbbinkandClaude Opus 5 41fed7413a fix(pricing): keep one unreadable model row from taking the node with it ...

Stored pricing is JSON from whatever wrote the row, so a legacy import or
foreign writer can leave a field that will not parse. Both places that convert a
row do it inside a loop, so one such row raised out of the whole operation: the
catalog listing returned nothing and the node advertised no models at all, and
the routing map came up empty at boot — on a later refresh the map it already
had went permanently stale instead.

Drop the row that cannot be read, log it by id, and keep serving and routing the
rest. It is unservable either way. The sibling loop over override-only rows in
the mapping builder already did this; the two now match.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011cKHVF5LA7TR5QuYi6ErLM

2026-08-25 16:33:44 +02:00

..

integration

fix(pricing): keep one unreadable model row from taking the node with it

2026-08-25 16:33:44 +02:00

unit

fix(pricing): keep one unreadable model row from taking the node with it

2026-08-25 16:33:44 +02:00

conftest.py

test: add return type annotations to cache fixtures for strict mypy

2026-08-17 23:26:52 +02:00

run_integration.py

dump wip stash

2025-08-06 20:31:55 -03:00