Skip to content

Fix CLI partial startup reporting when docling fails#1133

Open
Bortlesboat wants to merge 1 commit intolangflow-ai:mainfrom
Bortlesboat:codex/docling-startup-status
Open

Fix CLI partial startup reporting when docling fails#1133
Bortlesboat wants to merge 1 commit intolangflow-ai:mainfrom
Bortlesboat:codex/docling-startup-status

Conversation

@Bortlesboat
Copy link

Summary

  • stop the CLI from printing full startup success when container startup or docling startup fails
  • surface the docling failure reason when containers come up but docling does not
  • add a focused CLI regression test for the partial-start and full-success cases

Testing

  • PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 .venv/bin/python -m pytest tests/unit/test_cli.py --noconftest -q -p pytest_asyncio

Closes #1102

@github-actions github-actions bot added community backend 🔷 Issues related to backend services (OpenSearch, Langflow, APIs) tests and removed community labels Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend 🔷 Issues related to backend services (OpenSearch, Langflow, APIs) tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: CLI reports “All services started” even when docling-serve is stopped

1 participant