-
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
[ML] Fixes race condition where chart tooltip could be hidden. #23270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ven if it should be shown.
Pinging @elastic/ml-ui |
9 tasks
💚 Build Succeeded |
peteharverson
approved these changes
Sep 18, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jgowdyelastic
approved these changes
Sep 19, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
walterra
added a commit
to walterra/kibana
that referenced
this pull request
Sep 19, 2018
…ven if it should be shown. (elastic#23270) - Even with the check if fadeTimeout was set in show(), I could reproduce race conditions where a new tooltip would disappear again, because a previous fadeTimeout would trigger and set the new tooltips display to none. - This PR fixes it by adding a non-asynchronous visible flag to mlChartTooltipService to check if the tooltip should stay visible if fadeTimeout triggers.
walterra
added
bug
Fixes for quality problems that affect the customer experience
non-issue
Indicates to automation that a pull request should not appear in the release notes
labels
Sep 19, 2018
walterra
added a commit
that referenced
this pull request
Sep 20, 2018
…ven if it should be shown. (#23270) (#23308) - Even with the check if fadeTimeout was set in show(), I could reproduce race conditions where a new tooltip would disappear again, because a previous fadeTimeout would trigger and set the new tooltips display to none. - This PR fixes it by adding a non-asynchronous visible flag to mlChartTooltipService to check if the tooltip should stay visible if fadeTimeout triggers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Anomaly Detection
ML anomaly detection
Feature:ml-results
legacy - do not use
:ml
non-issue
Indicates to automation that a pull request should not appear in the release notes
v6.5.0
v7.0.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even with the check if
fadeTimeout
was set inshow()
, I could reproduce race conditions where a new tooltip would disappear again, because a previousfadeTimeout
would trigger and set the new tooltipsdisplay
tonone
.This PR fixes it by adding a non-asynchronous
visible
flag tomlChartTooltipService
to check if the tooltip should stay visible iffadeTimeout
triggers.Part of #22642.