-
-
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
I'm getting this, what might be the problem. #63
Comments
Got this while installing. npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see request/request#3142 |
Warnings during installation are fine, you can ignore those. Can you enable debug mode through the config? I can't really pinpoint at what point the bot is attempting to send a message in your instance, so it would be helpful if you could recreate it and include the relevant debugger info as well |
Got this. [DEBUG] [] |
You need to specify the link before the |
I was verifying w an instock link. |
Format the command like this: |
Still not working. only the !help command works. Got this message now. (node:54764) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag |
There should be more to that message than just that. Is there more debug output/error output before or after that message? |
I'm not sure, that may be a |
I've tried all, still does not work for me. |
That is very very odd. Are the error messages different depending on the command? |
Yes, it says Discord API error w everything, maybe some problem w Discord connection. I've verified the token and its the same as on the developer portal. Does the bot still work for you? |
If it was a problem with the API itself it would be giving a different error. Your empty message error suggests there is data that isn't being output somewhere, which could happen for a myriad of reasons. |
Would it be because of permissions, will try creating the application bot again. |
It very likely is not about permissions unfortunately |
Can you name some, I could reallly use this monitor! |
Well in this instance I believe it could be a problem with the data being returned from Amazon, perhaps a page is loading correctly or something. Was it working beforehand at all? Or was this happening as soon as you set it up? |
This has been happening since i set it up. Does the monitor still work for you? |
I tried w the Linux district again it didn’t work. Will try again tomorrow and w a fresh clone. Don’t know what’s going wrong. Maybe something to do w region? Shouldn’t be a problem though. |
Shouldn't be anything to do with the region, maybe that error involving the temp directory not being able to made could be related but I would have no idea how to fix that, since I've never seen it before, and you may have to go on a bit of a Googling adventure to figure that one out. |
Works for me now, the problem was with the permissions var in the config file. Also, how many products can I track w this? |
Also, does it need any proxies and whats the lowest refresh delay it can handle? |
You can technically track any amount of items, although that may start bogging your machine down performance wise, so judge based off of your computer resources. It does not require proxies but it is much more effective if you use them. With proxies you can bring down refresh delays to less than a minute although that too could cause performance issues, so just judge the best you can. |
(node:12156) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdtemp 'C:\Users\adity\AppData\Local\Temp;C:\Users\adity\AppData\Local\Programs\Python\Python37-32\Script\puppeteer_dev_chrome_profile-XXXXXX'
(Use
node --trace-warnings ...
to show where the warning was created)(node:12156) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:12156) [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.
(node:12156) UnhandledPromiseRejectionWarning: DiscordAPIError: Cannot send an empty message
at RequestHandler.execute (C:\Users\adity\Desktop\AmazonMonitor-master\node_modules\discord.js\src\rest\RequestHandler.js:154:13)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async RequestHandler.push (C:\Users\adity\Desktop\AmazonMonitor-master\node_modules\discord.js\src\rest\RequestHandler.js:39:14)
(node:12156) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)The text was updated successfully, but these errors were encountered: