Skip to content
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

[8.x] [ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available (#193890) #194527

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…and Analytics Map when no jobs are available (elastic#193890)

## Summary

Fix for [elastic#138193](elastic#138193)
I didn't find any relation between user permissions and the issue.
The error mentioned in the issue doesn't come from the ML package and is
unrelated to the problem.
The view was visible due to the initial state of `jobsExist`. Added
additional loading state to prevent screen flickering.

Disabled automatic display of the job selection flyout when no jobs are
available.

After:

https://github.com/user-attachments/assets/a8c6e5e2-ebcc-4320-b5be-f586ca6c0672
(cherry picked from commit a2e995a)
@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
ml 4.6MB 4.6MB +138.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @rbrtj

@kibanamachine kibanamachine merged commit f14c419 into elastic:8.x Oct 1, 2024
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants