Prevent simultaneous task failures multiple archive calls #1008
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.
If multiple tasks fail simultaneously, they will all attempt to call
beeflow.wf_manager.resources.wf_update.archive_workflow
. This will succeed for the first task that makes the call, but then lead to an endless loop of calls for the other tasks that error since the workflow folder will no longer exist in.beeflow/workflows
.This solves that problem by checking the workflow state does not begin with
Archived
when attempting to archive a failed workflow.db.workflows.get_workflow_state
seems to be the only way to do this once a workflow has been archived.I put this check where a failed task would call
archive_fail_workflow
, but potentially this could be inarchive_workflow
directly.Needs a test before removing
WIP
.