-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
[WIP] mission_result split into mission_status and navigator_status #9747
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
this PR is still valid, or at least the part the tries to fix this current bug: #9746 |
Needs to be rebased badly. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Closing as stale. |
The navigator message
mission_result
has become overloaded to contain both general navigator status, mission feasibility, and mission status. This has resulted in some confusion in both logs and usage from commander.This PR splits mission_result into a general navigator_status message, and a mission_status that's specific to the planned dataman stored mission.