You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code I have is designed to spin up a Discord client, do something over the API, and then close the client and end the script. It catches any exceptions and lets them to bubble up to crash the script in case of errors. It's supposed to work as a one-time job, not as a long-running bot. This code has worked correctly for several years now. It still does, but with 2.5.0 it started to produce errors which indicate something suddenly ain't right.
Actual Results
Getting errors which indicate something suddenly ain't right.
Intents
not relevant, but it's Intents(guilds=True, members=True, message_content=True)
System Information
Python v3.11.8-final
py-cord v2.5.None-final
aiohttp v3.9.3
system info: Darwin 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:27 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8103
Checklist
I have searched the open issues for duplicates.
I have shown the entire traceback, if possible.
I have removed my token from display, if visible.
Additional Context
I wanted to figure out what commits in pycord caused the errors, but there's 262 new commits in the new version and that's just too many for me to go through 🤯 So just hoping here you might have a hunch what could be the issue.
The text was updated successfully, but these errors were encountered:
Summary
After upgrading to 2.5.0, my program emits unexpected errors to log output.
Reproduction Steps
The code below works correctly with 2.4.1 and all previous versions:
After upgrading to 2.5.0, it produces the following logging at the end of the output:
Minimal Reproducible Code
No response
Expected Results
The code I have is designed to spin up a Discord client, do something over the API, and then close the client and end the script. It catches any exceptions and lets them to bubble up to crash the script in case of errors. It's supposed to work as a one-time job, not as a long-running bot. This code has worked correctly for several years now. It still does, but with 2.5.0 it started to produce errors which indicate something suddenly ain't right.
Actual Results
Getting errors which indicate something suddenly ain't right.
Intents
not relevant, but it's Intents(guilds=True, members=True, message_content=True)
System Information
Checklist
Additional Context
I wanted to figure out what commits in pycord caused the errors, but there's 262 new commits in the new version and that's just too many for me to go through 🤯 So just hoping here you might have a hunch what could be the issue.
The text was updated successfully, but these errors were encountered: