lukaszraczylo ce39b8eb37 fix(registry): retry failed startup discovery once in the background ...

A provider whose discovery failed during the warm fill at pod start
went without discovered models for a full discovery interval, which is
1 hour by default. It also stayed that way until a request arrived
after the interval. Production logs showed this for openai-audio and
anthropic when outbound calls were slow at startup.

A provider that fails the warm fill now gets one background retry
after 10s. The retry has its own timeout and uses the same refresh
bookkeeping. It is skipped when a refresh is already in flight or has
finished since the warm fill, and it is not scheduled when the parent
context was canceled. A recovery logs one INFO line. If the retry also
fails, the existing breaker behaviour applies unchanged.

The retry delay and the warm-fill timeout can be set per registry for
tests. yaegi-check probes the retry under the interpreter.

Claude-Session: https://claude.ai/code/session_01V5jYJNxpDFdJkyyExpADrv

2026-09-24 06:04:43 +01:00

..

admin_redesign.go

test(admin): probe the statistics endpoints under Yaegi and across replicas

2026-09-23 16:40:59 +01:00

go.mod

ci: run yaegi-check and the pricing-sync tests on pull requests

2026-09-23 09:44:32 +01:00

go.sum

ci: run yaegi-check and the pricing-sync tests on pull requests

2026-09-23 09:44:32 +01:00

main.go

fix(registry): retry failed startup discovery once in the background

2026-09-24 06:04:43 +01:00