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

Robot status not updating reliably during heartbeat handling #1383

Open
andchiind opened this issue Jan 31, 2024 · 3 comments
Open

Robot status not updating reliably during heartbeat handling #1383

andchiind opened this issue Jan 31, 2024 · 3 comments
Labels
backend Backend related functionality bug Something isn't working stale This issue or pull request already exists

Comments

@andchiind
Copy link
Contributor

andchiind commented Jan 31, 2024

Describe the bug
Robots often get stuck in busy even though Isar reports both the missionStatus as being idle and robotStatus as being available. This is because we do not reach the end of 'OnIsarRobotStatus' even when the status is not consistent. This could also be an Isar issue where the event is not sent each time it should be.

To Reproduce
The robot gets stuck in busy when, for instance, Isar completes a mission as soon as it's received. This happens for instance when localisation is not required for the given Isar instance. Currently the workaround is to make Isar sleep briefly after receiving such missions.

Expected behavior
If Isar reports itself as being available, then this should be relayed to the Flotilla data model in when looking at the heartbeat messages.

Screenshots

@andchiind andchiind added bug Something isn't working backend Backend related functionality labels Jan 31, 2024
@andchiind andchiind changed the title Update Robot status during heartbeat handling Update Robot status reliably during heartbeat handling Feb 1, 2024
@andchiind andchiind changed the title Update Robot status reliably during heartbeat handling Robot status not updating reliably during heartbeat handling Feb 1, 2024
@oysand oysand added this to the Ready for users milestone Apr 28, 2024
@aeshub
Copy link
Contributor

aeshub commented Jun 28, 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 Jun 28, 2024
@Christdej Christdej removed the stale This issue or pull request already exists label Aug 5, 2024
@Christdej
Copy link
Contributor

Waiting for new status solution in ISAR

@aeshub
Copy link
Contributor

aeshub commented Oct 13, 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 Oct 13, 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 stale This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants