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

Error EISDIR: illegal operation on a directory, read #5

Closed
ehmicky opened this issue May 18, 2020 · 4 comments
Closed

Error EISDIR: illegal operation on a directory, read #5

ehmicky opened this issue May 18, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@ehmicky
Copy link
Contributor

ehmicky commented May 18, 2020

The following error happens in some build:

Inlining sources failed.
EISDIR: illegal operation on a directory, read 
    fs.js:497:3 Object.readSync
    fs.js:322:20 tryReadSync
    fs.js:359:19 Object.readFileSync
    /opt/build/repo/node_modules/inline-source/lib/load.js:19:41 
    /opt/build/repo/node_modules/inline-source/lib/load.js:12:10 load
    /opt/build/repo/node_modules/inline-source/lib/run.js:17:17 
    /opt/build/repo/node_modules/inline-source/lib/run.js:14:13 run
    /opt/build/repo/node_modules/inline-source/index.js:44:15 

Do you know what this might be?

@Tom-Bonnike Tom-Bonnike added the bug Something isn't working label May 18, 2020
@Tom-Bonnike
Copy link
Owner

Tom-Bonnike commented May 18, 2020

It’s probably because a link/href/src it’s trying to inline seems to be pointing to a directory instead of a file.

This is the line that is failing, when trying to read a “source” (a file that inline-source tries to inline), and that error means it’s trying to read a directory instead of a file.

Is the project open-source? Do you have more info, like the file name, maybe?

@Tom-Bonnike
Copy link
Owner

Tom-Bonnike commented May 22, 2020

Any more info on this @ehmicky? Does it happen on a lot of projects?

Would you rather I try to catch this error and stop trying to inline the file? I think letting the build fail is actually what I’d expect as a user.

@ehmicky
Copy link
Contributor Author

ehmicky commented May 22, 2020

No, it only happened once in that build. Unfortunately, the repository is private and the build logs are not giving out additional information.

@Tom-Bonnike
Copy link
Owner

OK. I’ll close for now, happy to re-open if you start seeing it on more projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants