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

Make ApplyLargoSession job more robust against errors #198

Merged
merged 1 commit into from
Nov 27, 2024
Merged

Conversation

mzur
Copy link
Member

@mzur mzur commented Nov 27, 2024

If a job failed for some other reason than an exception during saving, the largo_job_id was not cleaned up and no error was shown. This is handled more robustly now. Also we need a mechanism to prevent re-running of the failed job. Otherwise unexpected changes could be applied. The exprected behavior is now that the user is shown the error message and they try to save the session again. The old job should be discarded then.

If a job failed for some other reason than an exception during
saving, the largo_job_id was not cleaned up and no error was
shown. This is handled more robustly now. Also we need a mechanism
to prevent re-running of the failed job. Otherwise unexpected changes
could be applied. The exprected behavior is now that the user is
shown the error message and they try to save the session again.
The old job should be discarded then.
@mzur mzur merged commit 75f38d1 into master Nov 27, 2024
2 checks passed
@mzur mzur deleted the patch-1 branch November 27, 2024 09:50
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.

1 participant