You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem including expected versus actual behavior:
In certain cases you can get into a broken state with ML's frontend routing
Steps to reproduce:
Open ML app by click on ML icon in nav
Click ML icon again
Click on any of the ML tabs (eg "Anomaly Detection")
ML app disappears, only blank screen shows
Errors in browser console (if relevant): No errors
This may be related to #53692 which a fix was made available in #56705.
I see that ML is still using a HashRouter. It is recommended to switch to the regular BrowserRouter and set up redirects when a hash is detected on the root route. That may help solve the problem.
The text was updated successfully, but these errors were encountered:
Clicking the ML sidebar icon while inside ML causes the trigging of onAppLeave but it doesn't actually leave the ML app.
We have clean up code in onAppLeave which is run and so the ML app is left in a broken state.
This is the behaviour that is being seen in this issue. Converting to BrowserRouter doesn't fix it.
I've been informed that using onAppLeave for plugin clean up is not correct. So please ignore the previous comment.
This issue can be easily resolved by moving our clean up code out of onAppLeave
Kibana version: master
Browser version: Chrome 80
Browser OS version: macOS Catalina
Description of the problem including expected versus actual behavior:
In certain cases you can get into a broken state with ML's frontend routing
Steps to reproduce:
Errors in browser console (if relevant): No errors
This may be related to #53692 which a fix was made available in #56705.
I see that ML is still using a HashRouter. It is recommended to switch to the regular BrowserRouter and set up redirects when a hash is detected on the root route. That may help solve the problem.
The text was updated successfully, but these errors were encountered: