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

ECONNRESET, user aborted the request #4827

Closed
1 task
Twiggeh opened this issue Sep 17, 2020 · 0 comments
Closed
1 task

ECONNRESET, user aborted the request #4827

Twiggeh opened this issue Sep 17, 2020 · 0 comments

Comments

@Twiggeh
Copy link

Twiggeh commented Sep 17, 2020

*Please describe the problem you are having in as much detail as possible:
After running a bot for ~ 5 hours or more, the send function likes to start "failing". It fails on this particular handle, not in any other handler.

User aborted a request

Include a reproducible code sample here, if possible:
I don't know if its reproducible, this one send is the only one that fails with a ~ 70% success rate.
All other sends are fine.

// basic version
const studentMessage = ({tag, content, url}) =>
({
    content: `**Student :** \`${tag}\`
                  **Message :** ${content}`,
   files:       [url] 
});

const result = await Promise.allSettled([
   // fails after the bot ran for ~ 5 hours or more, doesn't fail before that
    qTicket.coach.send(studentMessage(qTicket)),
  ]);

Further details:

  • discord.js version: "discord.js": "^12.2.0",
  • Node.js version: v14.9.0
  • Operating system: Linux x64 5.4.57-1-MANJARO and Ubuntu 20.04.1 LTS, 5.4.0-47-generic
  • Priority this issue should have – please be realistic and elaborate if possible:

Normal priority ? I can imagine that this is a pretty annoying thing that users might run into - It is "solved" by restarting the bot every couple of hours, but that isn't really a viable option, even if the bot is stateless. I would rather not have to do that :D

Relevant client options:

  • partials: none
  • gateway intents: none
  • other: none
  • I have also tested the issue on latest master, commit hash:
@iCrawl iCrawl closed this as completed Dec 12, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 9, 2023
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