Repository navigation
run-fargate — includeFiles with glob/wildcard patterns causes TypeError: eachDone is not a function #3756
daswathGori
started this conversation in
Artillery
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
When using includeFiles with glob/wildcard patterns (e.g., ../processors/**) in a config file passed to artillery run-fargate, the test fails with TypeError: eachDone is not a function during the S3 sync step.
Specifying each file individually (without globs) works correctly.
Version info
Steps to reproduce
Config file (dev.yml):
Command:
artillery run-fargate --region us-west-2 --count 1 --config config/dev.yml scenarios/my-scenario.ymlExpected behavior
Artillery bundles all files matching the glob patterns and uploads them to S3 for the Fargate workers.
Actual behavior
Root cause
In create-test.js line 136 ,
A.eachLimitis called with anasynciterator function:The bundled version of the async library uses wrapAsync which detects the async function and doesn't pass a callback — the async function's returned promise is used instead. So eachDone is always undefined.
This only triggers when glob patterns expand to multiple files (the iteration path). Individual file paths seem to bypass the syncS3 iteration or only produce a single item that doesn't hit this code path.
Workaround
List each file individually in includeFiles without glob patterns:
This works correctly but requires manual maintenance when adding new files.
All reactions