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

Fail mission when ISAR connection is lost #1054

Closed
wants to merge 4 commits into from

Conversation

andchiind
Copy link
Contributor

@andchiind andchiind commented Oct 12, 2023

Closes #1044

This PR fixes stopping the ongoing mission when connection to ISAR is lost, as well as an error that occurs when ISAR is started again. Errors were occuring since db context objects were taken out of scoped services and then used again from hosted services, which causes database errors since they are unable to verify that the object being modified is the same as before.

We still get a failed POST if we stop the mission as soon as we lose ISAR connection. I would like to create a banner alert for this, but I will then first wait for the failed request alert banner PR to be merged #1018 .

@andchiind andchiind added bug Something isn't working backend Backend related functionality labels Oct 12, 2023
@andchiind andchiind self-assigned this Oct 12, 2023
@andchiind andchiind force-pushed the 1044-bad-gateway branch 2 times, most recently from 933f2ce to 7780f55 Compare October 12, 2023 11:37
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

Successfully merging this pull request may close these issues.

Bad gateway returned if mission stopped after isar stops
2 participants