mikaelbr / gulp-notify

gulp plugin to send messages based on Vinyl Files or Errors to Mac OS X, Linux or Windows using the node-notifier module. Fallbacks to Growl or simply logging
MIT License
591 stars 40 forks source link

gulp-notify: [Error in notifier] Error in plugin 'gulp-notify' #87

Open mort3za opened 9 years ago

mort3za commented 9 years ago

I always get this error (some seconds after a successful notify). What is it?

gulp-notify: [Error in notifier] Error in plugin 'gulp-notify'
Message:
    Command failed:
Details:
    killed: false
    code: 3
    signal: null

My notify settings:

.pipe(notify({
      "title": "ProjectX",
      "onLast": true,
      "wait": true,
      "message": 'Yep'
    } ))

OS: Windows 8.1 x64

mort3za commented 9 years ago

After updating nodejs to 0.12.7 x64, I see more details on error:

Message:
    Command failed: C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\assets\gulp.png -m Yep -t Project - build done -q true -w true

Details:
    killed: false
    code: 3
    signal: null
    cmd: C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\assets\gulp.png -m Yep -t Project - build done -q true
-w true
vovayatsyuk commented 8 years ago

Hi, I have the same issue.

The error is raised, when wait option is used (Just before timeout event should be triggered).

Message:
    Command failed: d:\www\dev\rb\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p d:\www\dev\rb\node_modules\gulp-notify\assets\gulp.png -m d:\www\dev\rb\sw\core\bin\core-2016-02-29.zip kB -t Done -q true -w true

Details:
    killed: false
    code: 3
    signal: null
    cmd: d:\www\dev\rb\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p d:\www\dev\rb\node_modules\gulp-notify\assets\gulp.png -m d:\www\dev\rb\sw\core\bin\core-2016-02-29.zip kB -t Done -q true -w true

I've tried to run d:\www\dev\rb\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p d:\www\dev\rb\node_modules\gulp-notify\assets\gulp.png -m d:\www\dev\rb\sw\core\bin\core-2016-02-29.zip kB -t Done -q true -w true in terminal and it works just fine.

vovayatsyuk commented 8 years ago

This is a bug in https://github.com/mikaelbr/node-notifier: mikaelbr/node-notifier#97

The following code causes the same error:

var notifier = require('node-notifier');

notifier.notify({
  title: 'My awesome title',
  message: 'Hello from node, Mr. User!',
  sound: true,
  wait: true
}, function (err, response) {
  console.log(err);
});
{ [Error: Command failed: d:\www\dev\rb\node_modules\node-notifier\vendor\toaster\toast.exe -m Hello from node, Mr. User! -t My awesome title -w true
]
  killed: false,
  code: 3,
  signal: null,
  cmd: 'd:\\www\\dev\\rb\\node_modules\\node-notifier\\vendor\\toaster\\toast.exe -m Hello from node, Mr. User! -t My awesome title -w true' }
Nepomuseno commented 5 years ago

Alguien sabe como resolver esto?

Nepomuseno commented 5 years ago

Después de actualizar nodejs a 0.12.7 x64, veo más detalles sobre el error:

Message:
    Command failed: C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\assets\gulp.png -m Yep -t Project - build done -q true -w true

Details:
    killed: false
    code: 3
    signal: null
    cmd: C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\node_modules\node-notifier\vendor\toaster\toast.exe -onLast true -p C:\xampp2\htdocs\nik\joomfa\node_modules\gulp-notify\assets\gulp.png -m Yep -t Project - build done -q true
-w true

Tengo el mismo error, sabes como resolverlo?

MrEichi commented 5 years ago

Had the same issue. You need to execute gulp/npm with admin rights to get it to work.

Giovancruz commented 1 year ago

Same error here, looks like it's not installing the dependency. Running npm with admin privileges shouldn't be a solution.