gulp-notify: [Error in notifier] Error in plugin 'gulp-notify' Server did not respond
Closed this issue · 2 comments
Notifications are working properly, however and error is thrown in the terminal. See below:
gulp-notify: [Error in notifier] Error in plugin 'gulp-notify' Server did not respond
I investigated this some just now, and my working theory is due to the growler dependency that is used by node-notifier (module for actually sending notifications) to handle Growl messages.
From the source code:
https://github.com/betamos/Node-Growler/blob/master/lib/growler.js#L386-L389
It seems as if the callback is triggered multiple times as the socket connection timeouts in addition to when the socket is closed by the remote. Haven't confirmed this yet, but I'll have to try out Growl on mac.
I've added simple checking for multiple callbacks from the growler dependency here: mikaelbr/node-notifier@b0165ae
Hope this works some. Sometimes the "Server did not respond" callback might be the first one to get sent, and one can see this error but I figure the timeout will happen after close in most cases.
I'll look more into and maybe send a PR to the growler dependency to have a more robust and permanent solution.