-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
[BUG] UnhandledPromiseRejection #112
Comments
Has it worked before ever (and is there an existing watchlist? If so, try removing it)? What sort of system is it running on? What NodeJS version are you on (I recco trying on >= 20)? Do you really need to use the custom Chromium exec? Only use that if the bot is giving you issues about not being able to find it automatically |
Closing due to no response, and because I cannot reproduce |
Apologies for no response, I didn't see/notice your reply. It has never worked. |
I could give you a login on a system if needed? |
Need anything from me? |
I'll let you know if I do, this project isn't super high prio in my life these days, and I'd probably have to setup a FreeBSD VM/container environment just to test if that is relevant or not, so it may be a little while :P |
Describe the issue:
Start the bot, wait a few seconds, get an error "UnhandledPromiseRejection".
Running on a server.
I don't know if it is relevant, but the npm warned when installing:
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
Paste the contents of your
config.json
, excluding the token, here:Provide console output with debug mode enabled:
The text was updated successfully, but these errors were encountered: