-
Notifications
You must be signed in to change notification settings - Fork 159
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
Update cancel method #1038
Update cancel method #1038
Conversation
Pull Request Test Coverage Report for Build 6016014796
💛 - Coveralls |
if self._status != JobStatus.CANCELLED: | ||
raise RuntimeInvalidStateError( | ||
f"Failed to cancel job: {self._job_id} has status {self._status}" | ||
) |
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.
@merav-aharoni thoughts on this approach? Instead of manually setting this status to cancelled, we query the status from the server to check the actual status
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.
But i'm not sure if there's a better way - I don't like having to make another api call just to handle this relatively rare edge case where the job runs too quickly and cannot be cancelled.
Closing for now, will reopen when this problem arrises again or we have a better solution |
Summary
related to #1019
Details and comments
Fixes #