Skip to content
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

Return home scheduled when all missions aborted, but not started #1731

Open
andchiind opened this issue Sep 3, 2024 · 2 comments
Open

Return home scheduled when all missions aborted, but not started #1731

andchiind opened this issue Sep 3, 2024 · 2 comments
Labels
backend Backend related functionality bug Something isn't working

Comments

@andchiind
Copy link
Contributor

andchiind commented Sep 3, 2024

Describe the bug
When all missions are aborted (since the robot tried to run a mission on the wrong deck), a return home mission is still scheduled, and this mission is never started. The robot then remains localised at deck 2 (see screenshots).

To Reproduce
Schedule a mission on a different deck than the one currently running.

Expected behavior
The return to home mission should start in this case.

Screenshots
image
image
image

@andchiind andchiind added bug Something isn't working backend Backend related functionality labels Sep 3, 2024
@aeshub
Copy link
Contributor

aeshub commented Nov 6, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Nov 6, 2024
@andchiind
Copy link
Contributor Author

Should check if this is still the case

@andchiind andchiind removed the stale This issue or pull request already exists label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants