[Stack Monitoring] add loading state to nodes table#114709
Merged
neptunian merged 2 commits intoelastic:masterfrom Oct 13, 2021
Merged
[Stack Monitoring] add loading state to nodes table#114709neptunian merged 2 commits intoelastic:masterfrom
neptunian merged 2 commits intoelastic:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
In a previous PR, I removed the loading state from the angular version and didn't add one to the react version. This causes there to be no loading indicator when fetches are happening in the nodes listing table during table changes, and I believe it also causes the tests to be flakey that are waiting for the loading indicator to not exist. Since it never exists to begin with I think it finishes too early and causes a race condition when clicking a column to sort twice (see error). I think it could be the cause of this test failing sometimes.
Test