search

cubehouse / themeparks

Unofficial API for accessing ride wait times and schedules for Disneyland, Disney World, Universal Studios, and many more parks
MIT License
542 stars 125 forks source link

DisneylandParisMagicKingdom: UnhandledPromiseRejectionWarning #144

Closed VitalyChe closed 5 years ago

VitalyChe commented 5 years ago

Could you, please, check the issue

NODE_DEBUG=themeparks PARKID=DisneylandParisMagicKingdom npm run testonline

(node:13154) UnhandledPromiseRejectionWarning: 503: { "errors": [ { "typeId": "SERVICE_CALL_ERROR", "message": "Error calling Facility Service.", "systemErrorCode": "220038" } ] }

matounet51 commented 5 years ago

I have the same issue for DisneylandParisMagicKingdom and for DisneylandParisWaltDisneyStudios...

UnhandledPromiseRejectionWarning: 503: {
"errors": [
{
"typeId": "SERVICE_CALL_ERROR",
"message": "Error calling Facility Service.",
"systemErrorCode": "220038"
}
]
}
(node:568639) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an asy nc function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:568639) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are no t handled will terminate the Node.js process with a non-zero exit code.

tquentin38 commented 5 years ago

Same issue here ....

(node:1401) UnhandledPromiseRejectionWarning: 503: {
  "errors": [
    {
      "typeId": "SERVICE_CALL_ERROR",
      "message": "Error calling Facility Service.",
      "systemErrorCode": "220038"
    }
  ]
}
(node:1401) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1401) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
LouisForaux commented 5 years ago

Is the same here, after a downtime at Disneyland Paris of her servers.....

Probably a change about an endpoint ?

VitalyChe commented 5 years ago

The fix has been proposed!