Why can't SourceTree complete a clone using either ssh or http?

[sbkBscott]

SourceTree will fail a clone at the exact same file using ssh or http.  Only 46% of 14,211 files are obtained.  it it theorized here that SourceTree is choking on a path name that is heinously long.  Here is the path that fails with the attendant prepended and appended error strings:

error: unable to create file ui/middleware/node_modules/sequelize-cli/node_modules/gulp/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/node_modules/is-builtin-module/node_modules/builtin-modules/builtin-modules.json (No such file or directory)

Cloning from the command line works always.  This fails in the exact same place every tine no matter which protocol is used (so obviously not protocol dependent).

This is SourceTree 1.8.2.11 on Win10 with repository and client on CentOS systems.

[Seth]

When you begin your clone, you can select "Show Full Output" to see the exact git command that SourceTree is running. You might try copying that command verbatim to the command line.