cubehouse
commented
4 years ago Looks like the official app is doing the same thing. Need to handle this error more gracefully
Closed PhilippeP62 closed 4 years ago
cubehouse
commented
4 years ago Looks like the official app is doing the same thing. Need to handle this error more gracefully
PhilippeP62
commented
4 years ago Well as for some reason , I couldn't run 'npm run testonline' , I upgraded to the latest nodejs/npm and some other things are broken now :/
It's halloween 😁 I'll go back to this tomorrow ...
The official app seemed to work...
Le jeu. 31 oct. 2019 à 11:19, Jamie Holding notifications@github.com a écrit :
Looks like the official app is doing the same thing. Need to handle this error more gracefully
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cubehouse/themeparks/issues/255?email_source=notifications&email_token=ACYETUSUEQHIOJ4NY45ZSV3QRKWJ3A5CNFSM4JHHQTZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXGYEQ#issuecomment-548301842, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYETUVAZJHK7447MQRS44TQRKWJ3ANCNFSM4JHHQTZQ .
zacharyedwardbull
commented
4 years ago The API and app seems to be working again now, I found the official app wasn't working for most of this morning/afternoon.
Park Which park/resort has this issue?
Context
Describe the bug Retrieving waittimes crashes since this morning ...(changes nothing) I'll complete the info when I am not on my phone. Output
(node:9150) UnhandledPromiseRejectionWarning: 500: 500
(node:9150) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function with out a catch block, or by rejecting a promise which was not handled with .c atch(). (rejection id: 1)
(node:9150) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will t erminate the Node.js process with a non-zero exit code.