Skip to content
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

[BUG]: Better extraction failure notifications #5223

Merged

Conversation

dvince2
Copy link
Collaborator

@dvince2 dvince2 commented Oct 21, 2024

Description

There are two fixes here. Firstly, for #5154 we now send up an error message for the front end with a comma seperated list of what extraction services failed. Secondly for #5123 we forgot to send a Final message in the failure case so the extraction just sat forever at its last reported %

Resolves ##5123 and #5154

There are two fixes here. Firstly, for #5154 we now send up an error message for the front end with a comma seperated list of what extraction services failed. Secondly for #5123 we forgot to send a *Final* message in the failure case so the extraction just sat forever at its last reported %

Resolves #5123 and #5154
@dvince2 dvince2 requested a review from kbirk October 21, 2024 18:50
@dvince2 dvince2 linked an issue Oct 21, 2024 that may be closed by this pull request
Copy link
Member

@YohannParis YohannParis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@mwdchang mwdchang merged commit fc2348c into main Oct 22, 2024
5 checks passed
@mwdchang mwdchang deleted the 5154-bug-pdf-extraction-fails-but-still-returns-success branch October 22, 2024 13:13
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.

[BUG]: PDF extraction fails but still returns success
5 participants