Jim R. Wilson
jimbojw

Organizations

@sevenweeks
Jun 27, 2016
jimbojw commented on pull request npm/write-file-atomic#13
@jimbojw

Thanks @sheerun!

Jun 23, 2016
@jimbojw
trigger node reuses msg object
Jun 20, 2016
jimbojw commented on issue node-red/node-red#912
@jimbojw

Assuming this issue does not prevent Node-RED from starting up and functioning, could we somehow squelch this error message and instead print somet…

Jun 20, 2016
@jimbojw
Bump `node-red-node-serialport` version number.
Jun 16, 2016
jimbojw commented on issue node-red/node-red#908
@jimbojw

No problem! Impressive turn-around on tagging the issue :)

Jun 16, 2016
@jimbojw
Create default settings.js in the specified user directory
Jun 16, 2016
Jun 6, 2016
jimbojw commented on issue tessel/ambient-attx4#69
@jimbojw

Switching to Port B did not work for me—it only made the issue happen consistently. :/ I've successfully used the Relay module in Port B on my Tess…

May 31, 2016
jimbojw commented on issue tessel/ambient-attx4#70
@jimbojw

Update: Logging to the console is not the only way to trigger this behavior. It also happens when you attempt to interact with the Tessel's on-boar…

May 27, 2016
jimbojw commented on issue tessel/ambient-attx4#70
@jimbojw

Update: This still reliably happens for me as described here, but when I try Port B, it always fails, irrespective of whether I remove the console.…

May 26, 2016
jimbojw commented on issue tessel/ambient-attx4#69
@jimbojw

I've found that using console.log() before the ambient object's ready event will trigger this behavior. Documented here: #70

May 26, 2016
@jimbojw
console.log() before 'ready' event triggers update and connection failure
May 16, 2016
jimbojw commented on issue tessel/t2-cli#727
@jimbojw

Sounds good to me. I can't speak to the npm permission issues (4) because I haven't experienced the kind that you're describing, only the kind that…

May 16, 2016
jimbojw commented on issue yeoman/update-notifier#76
@jimbojw

The root cause of this issue is a bug in write-file-atomic which is used by configstore. I have documented it here: npm/write-file-atomic#11 In sho…

May 12, 2016
jimbojw commented on issue tessel/t2-cli#727
@jimbojw

Update: The following installation steps work for me (Ubuntu user with node installed via nvm): $ npm install -g t2-cli@0.0.20 $ sudo PATH=$PATH ba…

May 12, 2016
@jimbojw
Changes ownership to $USER on update.
May 11, 2016
jimbojw commented on issue tessel/t2-cli#714
@jimbojw

@rwaldron Thanks! I'll give it a try tomorrow morning.

May 11, 2016
jimbojw commented on issue tessel/t2-cli#730
@jimbojw

This blocking issue prevents Ubuntu users from troubleshooting their common installation problems. See #714

May 11, 2016
jimbojw commented on issue tessel/t2-cli#727
@jimbojw

Update: After hacking the logger to print stack before reporting the crash, I discovered that update notifier config file permissions were the caus…

May 11, 2016
jimbojw commented on issue tessel/t2-cli#714
@jimbojw

Also, FYI, users can't even currently discover that this is their problem because the output of crash reporter doesn't give them a fingerprint. $ t…

May 11, 2016
jimbojw commented on issue tessel/t2-cli#714
@jimbojw

I wonder why the users don't have access to something in their own home directory that probably wasn't there before... I have a hunch that it's b…

May 10, 2016
jimbojw commented on issue tessel/t2-cli#727
@jimbojw

Well, I don't actually have mine working yet. It's crashing with no indication as to the issue :) Given that the tessel-install-drivers.js just wri…

May 10, 2016
jimbojw commented on issue tessel/t2-cli#727
@jimbojw

The install-drivers script[1] does two things: It creates and writes to the file /etc/udev/rules.d/85-tessel.rules It runs the command udevadm co…

May 10, 2016
jimbojw commented on issue tessel/t2-cli#727
@jimbojw

I'm working through this right now, also trying to get to the simplest possible successful setup. I'm starting from non-root nvm with latest Node. $…