-
Notifications
You must be signed in to change notification settings - Fork 4.9k
fix: extract Docling async markdown result #3031
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
he-yufeng
wants to merge
1
commit into
HKUDS:dev
Choose a base branch
from
he-yufeng:fix/docling-markdown-extraction
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this default now reads Docling's
task_status, failed async conversions from docling-serve reportfailure(the API docs listfailureas the failed task state), but the defaultDOCLING_FAILED_VALUESbelow still only includesfailed,error. In that scenario the failure branch is never reached, so a bad conversion keeps polling untilDOCLING_MAX_POLLSand is reported as a timeout instead of surfacing the parser error; includefailurein the default/env example failure values.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Updated the Docling default failed states to include
failureand added a regression test so that atask_status: failureresponse raises the parser-service error immediately instead of polling until timeout.Validation:
python -m uv run pytest tests\test_pipeline_release_closure.py::test_parse_docling_uses_docling_serve_async_defaults tests\test_pipeline_release_closure.py::test_protocol_parse_service_extracts_docling_result_markdown tests\test_pipeline_release_closure.py::test_protocol_parse_service_raises_on_docling_failure_status tests\test_pipeline_release_closure.py::test_parse_docling_empty_service_result_raises_without_fallback tests\test_pipeline_release_closure.py::test_parse_mineru_empty_service_result_raises_without_fallback -qpython -m uv run ruff check lightrag\pipeline.py tests\test_pipeline_release_closure.pypython -m uv run ruff format lightrag\pipeline.py tests\test_pipeline_release_closure.py --checkpython -m py_compile lightrag\pipeline.py tests\test_pipeline_release_closure.pygit diff --check upstream/dev..HEAD