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: spawn ENAMETOOLONG on Windows 10 #20

Open
hypery2k opened this issue Oct 25, 2016 · 9 comments
Open

Error: spawn ENAMETOOLONG on Windows 10 #20

hypery2k opened this issue Oct 25, 2016 · 9 comments

Comments

@hypery2k
Copy link

Issues when using plugin on Windows 10, see mikaelbr/node-notifier#145

@hypery2k
Copy link
Author

or maybe this one is better: https://github.com/karma-runner/grunt-karma/pull/163/files

@guylando
Copy link

This issue prevents us from using this plugin

@meikeric
Copy link

meikeric commented Sep 10, 2017

Had this issue when building an app on Windows 10, disabled this plugin in webpack. Build fine...

@Gvozd
Copy link
Collaborator

Gvozd commented Nov 16, 2020

Is this a pressing problem?
try version 1.9.0 or newer

For this version, I managed to artificially call it by setting a message with a length of more than 32000 characters
If the message is longer than ~ 5000 characters, then there is no error, but the notification is no longer displayed

These are large enough messages, and I'm not sure if they are encountered in practice, especially 32000
If the problem persists, can you provide a reproducible example?

In any case, you can try to trim messages
But I would like to know what these limits depend on, and how to determine / set them, except for heuristic selection
Anyone have any ideas on this?

@Gvozd
Copy link
Collaborator

Gvozd commented Nov 29, 2020

reopen in the case of repetition

@Gvozd Gvozd closed this as completed Nov 29, 2020
@wolfingduck
Copy link

Hello,
I have the same problem:
[INFO] node:internal/errors:464
[INFO] ErrorCaptureStackTrace(err);
[INFO] ^
[INFO]
[INFO] Error: spawn ENAMETOOLONG
[INFO] at ChildProcess.spawn (node:internal/child_process:412:11)
[INFO] at spawn (node:child_process:698:9)
[INFO] at Object.execFile (node:child_process:325:17)
[INFO] at Object.module.exports.fileCommand (E:\jhispster\my_proj\node_modules\webpack-notifier\node_modules\node-notifier\lib\utils.js:76:13)
[INFO] at E:\jhispster\my_proj\node_modules\webpack-notifier\node_modules\node-notifier\notifiers\toaster.js:145:11
[INFO] at runMicrotasks ()
[INFO] at processTicksAndRejections (node:internal/process/task_queues:96:5) {
[INFO] errno: -4064,
[INFO] code: 'ENAMETOOLONG',
[INFO] syscall: 'spawn'
[INFO] }
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] -----------------------------

Anyone have any ideas on this?

@Gvozd
Copy link
Collaborator

Gvozd commented May 10, 2022

E:\ is phisical drive, or mounted to network share, or some sync tools, like google drive?

@Gvozd Gvozd reopened this May 10, 2022
@wolfingduck
Copy link

E:\ is a physical drive with file system nyfs.
I have already allowed my windows 10 pro to support long path

@Gvozd
Copy link
Collaborator

Gvozd commented May 11, 2022

Please run your webpack with env variable DEBUG="notifier", and pipe stdout to file
I need the latest [notifier path], [notifier options] from the log
Also I need your plugin configuration

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

5 participants