Skip to content
This repository has been archived by the owner on May 21, 2022. It is now read-only.

Crash bij nieuwe map #53

Open
maartenpeels opened this issue Apr 4, 2022 · 2 comments
Open

Crash bij nieuwe map #53

maartenpeels opened this issue Apr 4, 2022 · 2 comments

Comments

@maartenpeels
Copy link

Helaas lijkt de crash nog niet opgelost te zijn(#40), ik draai de headless bot in docker(laatste versie op master).

Error:

Nieuwe map geladen (reden: Windmolens)
Bad image path
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: 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(). The promise rejected with the reason "undefined".] {
  code: 'ERR_UNHANDLED_REJECTION'
}
@wimb0
Copy link

wimb0 commented Apr 4, 2022

Ik heb dezelfde melding na laden nieuwe image. Ook headless in docker.

Pixel geplaatst op 1370, 11! Volgende pixel wordt geplaatst om 6:53:19 PM.
Nieuwe map geladen (reden: Nog meer!!)
Nieuwe map geladen (reden: Captain Sparkless)
Bad image path
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: 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(). The promise rejected with the reason "undefined".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Node.js v17.8.0

@maartenpeels
Copy link
Author

Nu niet meer relevant, maar gebeurt alleen in docker. Als ik bot.js los draai niet

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

No branches or pull requests

2 participants