Found some tech debt for INSTCMD handling from v2.8.0-v2.8.2 #2860
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.
Some older tech debt found during work on solution for #2708 and planned follow-up to #2850 in particular:
drivers/dstate.c
:sock_arg()
: if INSTCMD returns STAT_INSTCMD_UNKNOWN, let it be known to the TRACKING clientsserver/upsd.{c,h}
: handle TRACKING value for STAT_CONVERSION_FAILEDERR UNKNOWN
rather thanERR INVALID-ARGUMENT
which applies more closely (at least from variants already defined in the NUT networking protocol)drivers/usbhid-ups.c
: anticipate NULLhidups_item->dfl
for commands; return STAT_INSTCMD_CONVERSION_FAILED if neither caller nor default parameter was availableval
with drivers that might put aNULL
value in thatdfl
field forHU_TYPE_CMD
entries (none seen in-tree so far)