-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Clicking home menu button shows blank page #144653
Comments
taking a look... |
I'm seeing these errors in the browser console:
|
@tsullivan I filed another for the minifed error as I was not sure if it was related to the blank page. If same root cause here is the other issue: #144642 |
@yuliacech @alisonelizabeth could you take a look? This could be related to a recent PR that touched this plugin: |
@yuliacech is going to look into this. Looks like a duplicate of #145283. |
This issue is consistently reproducible on cloud |
@yuliacech @alisonelizabeth |
@yuliacech @alisonelizabeth Found the problem. I set the debugger to catch caught exceptions and looked at what component was firing, and what its You're returning I think You can likely reproduce this locally by setting these props and state to this config. |
@liza-mae @yuliacech @alisonelizabeth Have we been able to confirm this as fixed in a SNAPSHOT or BC2, (though I'm not certain it made the cut-off for either) |
@clintandrewhall Yes, I tested the fix in the 8.6.0-SNAPSHOT on Cloud. BC2 doesn't include the fix though |
Kibana version: 8.6.0-SNAPSHOT
Elasticsearch version: 8.6.0-SNAPSHOT
Server OS version: Cloud
Browser version: Chrome Latest
Original install method (e.g. download page, yum, from source, etc.):
Staging
Description of the problem including expected versus actual behavior:
Clicking the Home menu turns up blank page.
Steps to reproduce:
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
The text was updated successfully, but these errors were encountered: