Skip to content
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

unhandledPromiseRejectionWarning #1

Open
nosarious opened this issue Mar 29, 2017 · 2 comments
Open

unhandledPromiseRejectionWarning #1

nosarious opened this issue Mar 29, 2017 · 2 comments

Comments

@nosarious
Copy link

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
Copy link
Owner

jmwohl commented Mar 31, 2017

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
Copy link
Author

nosarious commented Mar 31, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants