Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Copy Files Task / Publish Build Artifacts Task copy to invalid UNC OR drive root produces RangeError: Maximum call stack size exceeded Issue

See original GitHub issue

TFS Agent copy files task trying to create a directory on Network Mapped Drive (Z:\Releases, z drive is UNC Path as Mapped Network Drive) but getting this error: copyfiles_stack_size_exceeded

RangeError: Maximum call stack size exceeded String.slice (native) Object.dirname (path.js:795:17) mkdirSyncRecursive (D:\agent\tasks\CopyFiles\1.0.13\node_modules\shelljs\src\mkdir.js:7:22) mkdirSyncRecursive (D:\agent\tasks\CopyFiles\1.0.13\node_modules\shelljs\src\mkdir.js:16:3) mkdirSyncRecursive (D:\agent\tasks\CopyFiles\1.0.13\node_modules\shelljs\src\mkdir.js:16:3) mkdirSyncRecursive (D:\agent\tasks\CopyFiles\1.0.13\node_modules\shelljs\src\mkdir.js:16:3) mkdirSyncRecursive (D:\agent\tasks\CopyFiles\1.0.13\node_modules\shelljs\src\mkdir.js:16:3)

Issue Analytics

State:
Created 7 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

bryanmacfarlanecommented, Aug 16, 2016

Yep, that is a bad error which essentially means the share doesn’t exist or no permissions (agent runs as). We are changing this task to call robocopy.

0reactions

ericsciplecommented, Sep 7, 2016

Yes the fix for Copy Files will roll out with 106.