You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adjust some 4xx error codes that relate to internal loader handling for Propeller discovery and communication errors so that the external PropLoader can apply special processing to those cases. This relates to PropLoader Issue #28.
Currently, many Propeller loading errors simply use the code 400 and the PropLoader treats them all the same.
Specifically, some more general errors can keep the 400 coded response, but others, like "Propeller not found,", "Rx Handshake timeout," "Invalid Rx handshake," "Version response timeout," and "Invalid version response," should have unique codes, like 401, 402, 403, etc.
(some of these error messages are made up during this writing, but need to be errors if they don't already exist).
The text was updated successfully, but these errors were encountered:
Adjust some 4xx error codes that relate to internal loader handling for Propeller discovery and communication errors so that the external PropLoader can apply special processing to those cases. This relates to PropLoader Issue #28.
Currently, many Propeller loading errors simply use the code 400 and the PropLoader treats them all the same.
Specifically, some more general errors can keep the 400 coded response, but others, like "Propeller not found,", "Rx Handshake timeout," "Invalid Rx handshake," "Version response timeout," and "Invalid version response," should have unique codes, like 401, 402, 403, etc.
(some of these error messages are made up during this writing, but need to be errors if they don't already exist).
The text was updated successfully, but these errors were encountered: