Skip to content

fix(startup): downgrade LLM verify_connection failure to warning#1166

Merged
nicoloboschi merged 1 commit intomainfrom
fix/verify-connection-soft-fail
Apr 20, 2026
Merged

fix(startup): downgrade LLM verify_connection failure to warning#1166
nicoloboschi merged 1 commit intomainfrom
fix/verify-connection-soft-fail

Conversation

@nicoloboschi
Copy link
Copy Markdown
Collaborator

Summary

  • When the LLM provider is unavailable at startup (e.g. 429 quota exhaustion), the server now logs a warning and continues booting instead of crash-looping
  • Each distinct LLM config (default, retain, reflect, consolidation) is verified independently — a failure on one doesn't skip the others
  • Adds unit tests using mock provider to verify the soft-fail and happy-path behavior

Fixes #1147

Test plan

  • test_initialize_succeeds_when_verify_connection_fails — verify_connection raises, server still boots, warning logged
  • test_initialize_logs_warning_per_failing_config — two distinct configs fail, two separate warnings logged with config names
  • test_initialize_succeeds_when_verify_connection_succeeds — happy path, no warnings

…ead of crash

When the LLM provider is unavailable at startup (e.g. 429 quota exhaustion),
the server now logs a warning and continues booting instead of crash-looping.
This lets queued operations process once the provider becomes available.

Fixes #1147
@nicoloboschi nicoloboschi merged commit 9901aa1 into main Apr 20, 2026
53 of 54 checks passed
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.

LLM quota/429 errors get swallowed by retry wrapper — silent queue bloat + startup crash loop

1 participant