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

[BUG] UnhandledPromiseRejection #112

Open
risner opened this issue Jun 6, 2024 · 6 comments
Open

[BUG] UnhandledPromiseRejection #112

risner opened this issue Jun 6, 2024 · 6 comments

Comments

@risner
Copy link

risner commented Jun 6, 2024

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:

{
  "prefix":"!",
  "token":"works-changed-for-this-issue",
  "minutes_per_check":3,
  "seconds_between_check": 5,
  "url_params":{},
  "guild_item_limit":5,
  "cache_limit": 10,
  "required_perms":["permission_1", "permission_2"],
  "tld":"com",
  "auto_cart_link":true,
  "debug_enabled":true,
  "custom_chromium_exec":"/usr/local/bin/chrome"
}

Provide console output with debug mode enabled:

[MESSAGE]  Bot is ready!
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 "#<ErrorEvent>".
@risner risner changed the title [BUG] [BUG] UnhandledPromiseRejection Jun 6, 2024
@SpikeHD
Copy link
Owner

SpikeHD commented Jun 6, 2024

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

@SpikeHD
Copy link
Owner

SpikeHD commented Jun 14, 2024

Closing due to no response, and because I cannot reproduce

@SpikeHD SpikeHD closed this as completed Jun 14, 2024
@risner
Copy link
Author

risner commented Jun 14, 2024

Apologies for no response, I didn't see/notice your reply.

It has never worked.
There is no watchlist.
It's using node 20.
It's a FreeBSD system that I use other node projects.

@SpikeHD SpikeHD reopened this Jun 14, 2024
@risner
Copy link
Author

risner commented Jun 14, 2024

I could give you a login on a system if needed?

@risner
Copy link
Author

risner commented Jun 21, 2024

Need anything from me?

@SpikeHD
Copy link
Owner

SpikeHD commented Jun 21, 2024

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

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