Feature idle trail #72
Merged
Conversation
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
Contributor
|
This seems like a great addition, thanks. I will have a deeper look and merge it soon-ish |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
If tree don't have any running node, we can see nothing about deep nodes in monitor mode, only upper node state.
We can avoid the problem by increasing tick frequency, but it requires more computational resourses.
My solution is adding graphical styles for IDLE nodes, that was SUCCESS or FAILURE at current tick.
Gray-green - it is a IDLE status, that was SUCCESS in the past of the tick.
Gray-red - IDLE, that was FAILURE.
I.e. nodes stores it's last previous state and shows it, if current state is IDLE.
It is also works well with RUNNING status
and in replay mode