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

Set global recursion limit for shell commands #690

Merged
merged 1 commit into from Jul 27, 2021
Merged

Conversation

huddlej
Copy link
Contributor

@huddlej huddlej commented Jul 22, 2021

Description of proposed changes

Instead of setting the recursion limit for individual rules as issues with maximum recursion occur, we set the recursion limit as an environment variable prefixed to all shell commands in the workflow. This approach allows us to control the limit with a single variable and affect the entire workflow.

Related issue(s)

Fixes #689

Testing

  • Tested by CI

Release checklist

This is a minor change.

Instead of setting the recursion limit for individual rules as issues
with maximum recursion occur, we set the recursion limit as an
environment variable prefixed to all shell commands in the workflow.
This approach allows us to control the limit with a single variable and
affect the entire workflow.

Resolves #689
Copy link
Member

@jameshadfield jameshadfield left a comment

Choose a reason for hiding this comment

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

Tested using augur 12.0.0

@huddlej huddlej merged commit df6aa5c into master Jul 27, 2021
@huddlej huddlej deleted the set-recursion-limit branch July 27, 2021 03:51
joverlee521 added a commit to nextstrain/augur that referenced this pull request Apr 14, 2023
We've had to use the `AUGUR_RECURSION_LIMIT` environment variable to
bump the recursion limit for SARS-CoV-2 builds¹, mpox builds², and
our `nextstrain-jobs` definition in AWS Batch. From a general search of
the envvar across GitHub³, 10,000 looks like the default that others use
as well (although this may be influenced by our discussions⁴).

¹ nextstrain/ncov#690
² nextstrain/mpox#150
³ https://cs.github.com/?scopeName=All+repos&scope=&q=AUGUR_RECURSION_LIMIT%3D#328
joverlee521 added a commit to nextstrain/augur that referenced this pull request Apr 17, 2023
We've had to use the `AUGUR_RECURSION_LIMIT` environment variable to
bump the recursion limit for SARS-CoV-2 builds¹, mpox builds², and
our `nextstrain-jobs` definition in AWS Batch. From a general search of
the envvar across GitHub³, 10,000 looks like the default that others use
as well (although this may be influenced by our discussions⁴).

¹ nextstrain/ncov#690
² nextstrain/mpox#150
³ https://cs.github.com/?scopeName=All+repos&scope=&q=AUGUR_RECURSION_LIMIT%3D#328
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.

Large trees produce "maximum recursion limit" errors at multiple steps of the workflow
2 participants