unhandledPromiseRejectionWarning

[nosarious]

I am receiving node errors while attempting to use an openframeworks artwork I created which worked earlier.

I recently reinstalled Noobs on my raspberry pi and then installed openframe itself, which worked properly with the various shaders. I then installed openframe-of to be able to use the artwork I created but when I run them, I get errors (the node error number is not always the same)

I first updated and upgraded the raspberry pi installation. I installed openframe again, just in case there had been changes (it notified me that node 6.9.5 was now being used)

running an openframeworks artwork gave me this error:

(node:4814) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id:1): TypeError: Cannot read property 'download' of undefined

I installed openframe-of again (realizing that it may not actually be there after the openframe re-installation) Running an artwork gave me this error:

(node:4824) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id:1): TypeError: rest.client.Frame.Frame_upsert_patch_frames is not a function

I ... really don't understand what this could be. I usually have my tongue out the right side of my mouth while typing... should it be on the left?

[jmwohl]

Damn. Thanks for the heads up! I haven't looked at this extension in a while, and admittedly haven't tested it since the latest Openframe release. I did change the way downloads were happening, it may be related to that — I should have some time this weekend to track down the issue.

More soon...

[nosarious]

Oh! So you mean it might not be something my Linux-limited fumbling did with the underlying thinginess of openframe stuff? Whew!

On Mar 31, 2017, at 8:29 AM, Jonathan Wohl [email protected] wrote:

Damn. Thanks for the heads up! I haven't looked at this extension in a while, and admittedly haven't tested it since the latest Openframe release. I did change the way downloads were happening, it may be related to that — I should have some time this weekend to track down the issue.

More soon...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.