-
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
Fatal callback error with multiple report generations / notifications #19285
Comments
cc @elastic/kibana-design since it seems to be coming from the EUIGlobalToastList code. |
I can replicate in the |
not solved in kibana yet, re-opening |
Is this really a blocker for 6.3? In a psuedo-related conversation with @timroes he said our current backporting policy says we only backport critical security issues to 6.3 |
When running multiple report generation tasks in the background, which is probably a common use case, this fatal error can occur multiple times at random times. So it will interrupt any other work that is being done in the browser. Since this is new functionality that did not exist in 6.2.4, in this scenario it will cause the system to act flaky and it should be fixed in 6.3.0. It negatively impacts the user experience and could possibly result in work loss, this is why we decided it should be a blocker. |
closed by #19361 |
Kibana version: 6.3.0 BC6
Elasticsearch version: 6.3.0 BC6
Server OS version: OSX
Browser version: Chrome / Firefox
Browser OS version: Latest
Original install method (e.g. download page, yum, from source, etc.): Staging
Describe the bug:
Generating several reports at the same time can cause a fatal error to occur. It is not consistent in reproducing but I do see it happening multiple times. Since I see ToastList in the error message I believe this is to do with the notifications being generated by initiating multiple reports.
Steps to reproduce:
Install Elasticsearch, Kibana
Generate multiple reports, continue navigating in kibana
Sometimes while looking at one report in a tab or just navigating back to the report page a fatal error occurs.
The text was updated successfully, but these errors were encountered: