Closed aeshub closed 1 year ago
Use a sleep for demo purposes as a workaround untill a proper fix can be put in place.
Sleep has been put in place as a temporary solution to this issue. https://github.com/equinor/isar/commit/ce189ada782529ce75e2b5cd67ca6b58ee4b284e
This issue has automatically been marked as stale as there has been no activity for 60 days. Remove stale label or comment or this will be closed in 7 days.
Will be resolved by #274
This issue has automatically been marked as stale as there has been no activity for 60 days. Remove stale label or comment or this will be closed in 7 days.
This issue has automatically been marked as stale as there has been no activity for 60 days. Remove stale label or comment or this will be closed in 7 days.
Bug is still there
Did you try to remove this workaround @Christdej? As far as I can tell it is still there. Until further notice I will move this issue back to blocked.
Did not test, just saw that in the comments Morten wrote that it would be resolved by #274 , but apparently it was not.
We believe this can be removed now, by removing the workaround which was added in https://github.com/equinor/isar/commit/ce189ada782529ce75e2b5cd67ca6b58ee4b284e
Resolved by https://github.com/equinor/isar/pull/477
Describe the bug Flotilla will as of #224 miss the initial updates to mission, task and step status because ISAR starts the mission and fires the first MQTT messages before Flotilla is finished writing the initial report to the database. This is because the mission starts before ISAR returns the mission details to Flotilla.
To Reproduce Start a mission in ISAR from Flotilla. Easiest seen using isar-robot as all updates will fail because it's so fast.
Expected behavior Flotilla should receive and react to all updates once a mission has started.