-
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 network policy violation should not cause unhandled promise rejection #71481
Comments
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Hi @legrego what are the repro steps here, and what would you say is the expected result of the scenario that causes this? |
@tsullivan sorry for the vague report, I updated the issue description with reproduction steps. My expectation is that this error would be caught and logged somewhere in the promise chain, instead of getting raised as an uncaught promise rejection |
If we can show the error message in the screenshot itself, or as a warning message on the job we'll do that. Generally when anything causes the screenshot to fail, it makes the underlying issue hard to troubleshoot. It definitely should not cause the server to crash :) |
I think I have a fix with #71481, but I'm not sure the best way to test the fix. This will probably need a functional test that has that Canvas expression in a saved worksheet in a a test data archive. |
Puppeteer debug logs:
|
A PR went in to address this however, the issue still happens in dev mode due to: kibana/x-pack/plugins/reporting/server/browsers/chromium/driver/chromium_driver.ts Line 306 in e00d7d2
|
This error currently causes an unhandled promise rejection, which crashes Kibana when running in dev mode. This should be addressed so that the error is caught and handled correctly:
kibana/x-pack/plugins/reporting/server/browsers/chromium/driver/chromium_driver.ts
Line 229 in 6c62c68
Steps to reproduce:
via.placeholder.com
:via.placeholder.com
:The report will correctly fail, due to the network policy violation. However, when running in dev mode, this causes the Kibana server to crash, because the error thrown by the code above is not handled by the calling code.
I would expect this error to be caught and logged, rather than being uncaught and relying on the Kibana runtime to handle this.
The text was updated successfully, but these errors were encountered: