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
Describe the bug
When tasks complete and are reported on MQTT quickly then some of them are not processed fully by the relevant event handler. The log that the event has been processed is printed, but the effect is not seen in the database. In the screenshot we see the effect on the frontend, but it is not a signalR issue as it persists after refreshing.
Describe the bug
When tasks complete and are reported on MQTT quickly then some of them are not processed fully by the relevant event handler. The log that the event has been processed is printed, but the effect is not seen in the database. In the screenshot we see the effect on the frontend, but it is not a signalR issue as it persists after refreshing.
To Reproduce
Relevant ISAR settings used:
ISAR_ROBOT_STEP_DURATION_IN_SECONDS = 0.05
ISAR_ROBOT_MISSION_DURATION_IN_SECONDS = 0.05
ISAR_ISAR_ROBOT_STATUS_PUBLISH_INTERVAL = 0.025
The issue is also easiest to see with longer missions.
Expected behavior
By the time a mission is reported as completed, all tasks should have their statuses updated.
Screenshots

The text was updated successfully, but these errors were encountered: