-
Notifications
You must be signed in to change notification settings - Fork 37
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
Fix concurrency issues for updating robot object #1092
Merged
aeshub
merged 9 commits into
equinor:main
from
aeshub:fix-missions-being-set-to-wrong-status
Nov 2, 2023
Merged
Fix concurrency issues for updating robot object #1092
aeshub
merged 9 commits into
equinor:main
from
aeshub:fix-missions-being-set-to-wrong-status
Nov 2, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔔 Changes in database folder detected 🔔 |
aeshub
force-pushed
the
fix-missions-being-set-to-wrong-status
branch
5 times, most recently
from
November 1, 2023 13:17
3134b34
to
6837903
Compare
aeshub
changed the title
Fix missions being set to wrong status
Fix concurrency issues for updating robot object
Nov 1, 2023
oysand
reviewed
Nov 1, 2023
oysand
reviewed
Nov 1, 2023
oysand
reviewed
Nov 1, 2023
oysand
reviewed
Nov 2, 2023
aeshub
force-pushed
the
fix-missions-being-set-to-wrong-status
branch
from
November 2, 2023 08:49
6837903
to
c3a5b67
Compare
The log statement was in a location where it would always be called even if a mission had in fact not been completed yet.
This handling should no longer be required in the robot controller. It was also causing previously finished mission runs to be set as failed even though they had succeeded as the current mission for the robot had not been reset yet.
aeshub
force-pushed
the
fix-missions-being-set-to-wrong-status
branch
from
November 2, 2023 09:09
c3a5b67
to
d963446
Compare
Christdej
approved these changes
Nov 2, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1089