Skip to content

wildcard expansion triggering "argument too long" error #8305

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

Closed
2 tasks done
tom-brekke opened this issue Apr 15, 2025 · 1 comment · Fixed by #8307
Closed
2 tasks done

wildcard expansion triggering "argument too long" error #8305

tom-brekke opened this issue Apr 15, 2025 · 1 comment · Fixed by #8307
Labels
bug Something isn't working

Comments

@tom-brekke
Copy link
Contributor

Have you checked the docs?

Description of the bug

The wildcard-expansion in the gzip call here:

gzip -n ${prefix}.${out_ext}*

is running up against the limit on the maximum number of arguments in my OS.

I would like to replace it with something like this instead:

find . -name \"${prefix}.${out_ext}*[0-9]\" | xargs gzip -n

I've implemented this locally and it seems to work.
I'm beginning a PR that I'll link to presently.

Command used and terminal output

Relevant files

No response

System information

Nextflow version 24.10.5
HPC
slurm
Apptainer
Debian GNU/Linux
ampliseq version 2.13.0

@tom-brekke tom-brekke added the bug Something isn't working label Apr 15, 2025
@tom-brekke
Copy link
Contributor Author

Here's the PR: #8307

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant