-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Reporting] Give users better information when pdf fails #126171
[Reporting] Give users better information when pdf fails #126171
Conversation
Pinging @elastic/kibana-app-services (Team:AppServicesUx) |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
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.
LGTM
Reviewed the code within Github
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
) * raise pdf worker out memory error to common errors * not having a PDF buffer for a PDF report should fail the report * remove unused import * make it possible to format Reporting errors nicely * make pdf v1 behave the same way as v2 regarding not compiling a PDF * remove unused import Co-authored-by: Kibana Machine <[email protected]>
Summary
Today when a PDF fails to generate a buffer we report that as a warning to users. This contribution makes a failure to generate a PDF buffer fail the report and sends a formatted message back to the user if it was due to an out-of-memory condition in the worker thread.
Screenshots
Checklist