-
Notifications
You must be signed in to change notification settings - Fork 22
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
sr3 status fixes #1350 and #1352. #1355
Conversation
the problem was that there were multiple conditions to check to assign one of the new states and if the multiple conditions did not result in "down" or "disconnected" state... it would skip over a number of checks for *idle* state. So moved all the new states to a separate if above the exising series.
Test Results5 tests 0 ✅ 18s ⏱️ For more details on these errors, see this check. Results for commit 68fc9e9. |
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.
✅ Looks great! RS also signed off on the logics ;)
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.
Very alphabet (google owns me) |
close #1352
close #1350
For #1350, there was a tally missing from empry_metrics so that the post_retries were not being counted.
For #1350, added two states, disconnected is for when communications with the broker is broken. down is when data transfer connection is broken.
seems to work.