Repository navigation
fix(ui): follow the clients alone on the screen of a client when the cluster refuses its allocations - #188
Merged
Conversation
…cluster refuses its allocations
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes
The screen of a client no longer warns and polls every 2 seconds with a token that may read jobs in some namespaces only. It follows Allocation and Node in every namespace, a stream such a token is refused since hashicorp/nomad#25089.
Left as they are: the jobs of a node pool and screens with the session in all namespaces ask for every namespace too, and with such a token still warn and poll fast. They have no smaller set of topics to follow.
Closes #186
Checklist
make checkis greenfeat(ui): ...,fix(nomad): ...