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
However, it seems like no matter what the status is of the node before-hand, it will always be reported as online: false within the response's node object.
The node is online, then approve_routes displays the status as offline, then immediately shows online again.
Expected Behavior
The status of the node should not change.
Steps To Reproduce
Forgive me for using the annoying escape mechanics of windows powershell, but I can run this compound command. It checks a node and uses jq to parse the ".node.online" value. It returns true. Then it updates the node's approved routes, and prints out the same ".node.online" value. Finally, it performs the first request again just to check the node's true online status.
Uh oh!
There was an error while loading. Please reload this page.
Is this a support request?
Is there an existing issue for this?
Current Behavior
When sending a POST request to
/api/v1/node/<NodeID>/approved_routes
, the response is the node objectHowever, it seems like no matter what the status is of the node before-hand, it will always be reported as
online: false
within the response's node object.The node is online, then approve_routes displays the status as offline, then immediately shows online again.
Expected Behavior
The status of the node should not change.
Steps To Reproduce
Forgive me for using the annoying escape mechanics of windows powershell, but I can run this compound command. It checks a node and uses jq to parse the ".node.online" value. It returns true. Then it updates the node's approved routes, and prints out the same ".node.online" value. Finally, it performs the first request again just to check the node's true online status.
Environment
Runtime environment
Debug information
Just the above command output is sufficient.
The text was updated successfully, but these errors were encountered: