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

Oc 70 fix dance interface crash #53

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

vgupta-bdai
Copy link
Contributor

Improved error handling for execute_dance. The function now returns instantly if anything goes wrong (e.g. robot is estopped).

@vgupta-bdai
Copy link
Contributor Author

@spnsingh I just realized that this code relies on protobuf changes that come with v3.3.0 of the SDK. Everything was working fine from my side as I had previously updated the SDK on my local system. Seems to me like we'd need to park this PR till we update to v3.3.0. Let me know how you'd like me to handle this! Really sorry for not catching this earlier.

Copy link
Collaborator

@davidwatkins-bdai davidwatkins-bdai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

self, status: choreography_sequence_pb2.ChoreographyStatusResponse.Status
) -> bool:
"""Check the status message to see if dance is onging/completed, return True if dance is completed"""
ongoing_states = [
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these make sense to be defined here?

return True, "success"

start = time.time()
while time.time() - start < estimated_time_seconds + 0.2:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is the 0.2 coming from?

"Call to execute_choreography did not return completion state in stipulated time"
)

except CommandTimedOutError:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this being caught exclusively from L171? If so, is there a better way to handle this control flow?

@vgupta-bdai vgupta-bdai changed the title Oc 70 fix dance interface crash [DO NOT MERGE] Oc 70 fix dance interface crash Jul 12, 2023
@vgupta-bdai vgupta-bdai added the invalid This doesn't seem right label Jul 13, 2023
@vgupta-bdai vgupta-bdai marked this pull request as draft July 13, 2023 16:54
@vgupta-bdai vgupta-bdai changed the title [DO NOT MERGE] Oc 70 fix dance interface crash Oc 70 fix dance interface crash Jul 13, 2023
@vgupta-bdai vgupta-bdai removed the invalid This doesn't seem right label Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants