-
Notifications
You must be signed in to change notification settings - Fork 25
feat: timeouts #457
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
base: main
Are you sure you want to change the base?
feat: timeouts #457
Changes from all commits
f81a33e
0342b5c
841d242
75fd7f1
7abd709
e07c961
d5b7e18
111e53f
c2febff
cc46eed
83c5ed0
71c1976
6e60afe
7ce0580
699ddca
4e3c28f
a322f4d
641608f
c5ff6ad
208eb4a
7a0c4f3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| ######## | ||
| Errors | ||
| ######## | ||
|
|
||
| By default, whenever SPRAS runs into a container error (i.e. an internal | ||
| algorithm error), the full workflow will fail. However, there are | ||
| certain designated errors where we don't want this to be the case (at | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we make this a separate section that explains each error instead of putting it in parentheses (even though right now it is only timeouts). We can expand this in the future. |
||
| the moment, these designated errors are only container timeouts, but | ||
| this may be extended to heuristics in the future). | ||
|
|
||
| Due to the following design constraints: | ||
|
|
||
| - Snakemake does not have support for such errors (the closest being | ||
| ``--keep-going``, which unnecessarily runs failed runs) | ||
| - SPRAS occasionally outputs empty files as genuine output | ||
| - We need to log errors that happen for user knowledge | ||
|
|
||
| we opt to use a ``resource-info.json`` file, which keeps track of the | ||
| success/failure status at certain failable parts of the workflow. This | ||
| file contains whether or not this part of the workflow succeeded, and if | ||
| it failed, how it failed. | ||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,20 @@ | ||||||
| ########## | ||||||
| Timeouts | ||||||
| ########## | ||||||
|
|
||||||
| SPRAS allows for per-algorithm timeouts, specified under the global | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can you also add a sentence on what happens when timeout is not included? |
||||||
| configuration file. For example, to give the AllPairs algorithm a 1 day | ||||||
| timeout: | ||||||
|
|
||||||
| .. code:: yaml | ||||||
|
|
||||||
| - name: "allpairs" | ||||||
| include: true | ||||||
| timeout: 1d | ||||||
|
|
||||||
| The timeout string parsing is delegated to `pytimeparse | ||||||
| <https://pypi.org/project/pytimeparse/>`__, which allows for more | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| complicated timeout strings, such as ``3d2h32m``. | ||||||
|
|
||||||
| **NOTE**: This feature only works with docker and apptainer/singularity | ||||||
| at the time of writing. | ||||||
Uh oh!
There was an error while loading. Please reload this page.