-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cancel Mission on STOP #18
Cancel Mission on STOP #18
Conversation
0a6360e
to
00e4d8e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sounds good. I also agree that Missions in general should be cancelled on STOP command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests needed an approval to be ran automatically, so did that now. It seems like two of them are currently failing.
The changes look great now! I've emailed you about one more thing to discuss. Once we resolve that one, this one is good to go. |
Hey! Not sure if I got your email 🤔 |
After some recent re-evaluations we have thought that it might make more sense for the Mission task to actually be cancelled on Stop.
For example, you have a robot doing a mission of visiting many different locations, and then you press a big red Stop button: you expect the robot to stop, not to just skip the current location where it was going to and proceed to the next one. If you want to cancel only the current location, you do have the option to cancel that one task specifically, as long as you have
allow_skipping
enabledChanges:
cancel_on_stop=True