Introduce driver.state tracking
#1771
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
… before regular work [networkupstools#1767]
|
✅ Build nut 2.8.0.286-master completed (commit 8f86e60004 by @jimklimov) |
Member
Author
|
Got no comments (nor "vetoes") here or on mailing list during the week. |
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.
Closes: #1767
Closes: #1388
Split off from PR #1770 as a separate feature, and at that - one for NUT community to agree upon (new standard nut-names entry).
This change allows drivers to uniformly report (to NUT clients as well as a dstate entry that can be internally consulted by driver logic) whether they are at this moment initializing, reconnecting, updating info from the device, or just being quiet between work bursts.