Skip to content
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

ENAMETOOLONG #66

Closed
seflless opened this issue Jun 26, 2014 · 2 comments
Closed

ENAMETOOLONG #66

seflless opened this issue Jun 26, 2014 · 2 comments

Comments

@seflless
Copy link

I'm getting ENAMETOOLONG on trying to create this file via fsExtra.mkdirs:
ENAMETOOLONG
/Users/flaberge/dev/topperharley/work/507017973001/587bcadc-b170-41f3-bc3e-656be3fe5031/default

But using mkdir -p /Users/flaberge/dev/topperharley/work/507017973001/587bcadc-b170-41f3-bc3e-656be3fe5031/default via command line does work.

On the latest MacbookPro, on Yosemite. This looks to be coming from here or near in libuv, but I figured you might be familiar with the issue and more responsive.

@jprichardson
Copy link
Owner

This is bizarre, I thought unix path names could be up to 65535...

@seflless
Copy link
Author

I think for cross platform consistency it may be capped to 260. Windows restriction maybe? I didn't spend enough time going through libuv to get an exact answer.

Turns out I had a mismatch in some parameter order and was appending a function to my path which effectively added the function's body of code, blowing through the 260 characters. Doh.

Closing comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants