-
Notifications
You must be signed in to change notification settings - Fork 28
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
Crashes after being idle for a while #5
Comments
@dippnerd I've also encountered it once. Not sure though how to solve it. The problem seems to be in the npm package I'm using to execute applescript commands. |
Yeah, it doesn't seem specific to your program from what I can tell, but wanted to make sure it's not just me :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, it's me again, sorry! Just wondering if you've run into this. I've been leaving this running, music playing or not, but at some point (haven't narrowed down how long it takes) it errors out. The status seems to fall into an undefined state for some reason, but nothing changed on the machine, it's a Mac Mini sitting idle otherwise. I'm trying to familiarize myself with the various modules, but hoping you might have some insight.
Here is the output:
/Users/aaron/iTunes-Remote/node_modules/node-osascript/lib/index.js:14
stream.on('data', function( chunk ){
^
TypeError: Cannot read property 'on' of undefined
at bufferStream (/Users/aaron/iTunes-Remote/node_modules/node-osascript/lib/index.js:14:9)
at execute (/Users/aaron/iTunes-Remote/node_modules/node-osascript/lib/index.js:31:19)
at Object.execute (/Users/aaron/iTunes-Remote/node_modules/node-osascript/lib/index.js:69:5)
at osa.execute (/Users/aaron/iTunes-Remote/server/serverSideEvents.js:85:25)
at ChildProcess. (/Users/aaron/iTunes-Remote/node_modules/node-osascript/lib/index.js:49:7)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
The text was updated successfully, but these errors were encountered: