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
Currently the mechanism the /append waypoint uses to add a new Waypoint to the queue is unreliable. Change it to reconstruct the mission entirely like with a new mission.
See the PUSH section in client.py. Also, rename PUSH to something more sensible
Currently the /prepend endpoint is very slow, because it 1. obtains the queue from MissionPlanner, 2. constructs the new queue, and 3. sends it back to MissionPlanner. If this logic was handled entirely within client.py, the endpoint, and the time it takes for the new queue to take effect, would be faster.
The mechanism for adding the prepended mission should be the same as above.
Reproduction steps
Call either endpoint
Expected behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
/append
waypoint uses to add a new Waypoint to the queue is unreliable. Change it to reconstruct the mission entirely like with a new mission.PUSH
section inclient.py
. Also, renamePUSH
to something more sensible/prepend
endpoint is very slow, because it 1. obtains the queue from MissionPlanner, 2. constructs the new queue, and 3. sends it back to MissionPlanner. If this logic was handled entirely withinclient.py
, the endpoint, and the time it takes for the new queue to take effect, would be faster.Reproduction steps
Call either endpoint
Expected behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: