I recently ran into a bug in fast-glob where it was setting concurrency: 0 in some environments. This triggers a nasty situation where all work is just queued up forever and fastq silently never makes progress.
It might be good to validate the concurrency parameter and not allow a value less than 1.
I recently ran into a bug in fast-glob where it was setting
concurrency: 0
in some environments. This triggers a nasty situation where all work is just queued up forever and fastq silently never makes progress.It might be good to validate the concurrency parameter and not allow a value less than 1.