aboutsummaryrefslogtreecommitdiff
path: root/discord/relationship.py
diff options
context:
space:
mode:
authorRapptz <[email protected]>2020-05-03 01:28:29 -0400
committerRapptz <[email protected]>2020-07-25 09:59:40 -0400
commite2f42597a5d81c048ac926c434e81f3997fedb7e (patch)
tree730c834e44e7144dcdafedeb8ec5dbbef08d0209 /discord/relationship.py
parentAdd shard related connection and resume events. (diff)
downloaddiscord.py-e2f42597a5d81c048ac926c434e81f3997fedb7e.tar.xz
discord.py-e2f42597a5d81c048ac926c434e81f3997fedb7e.zip
Handle Connection Reset by Peer connection errors.
This should work both on Windows and on Linux. Apparently these types of blips are considered normal for Discord. So rather than letting the reconnect logic handler expect these to be catastrophic, it should handle it specially so it doesn't waste an IDENTIFY for what ultimately should just be a small networking blip. This also makes it less noisy for the end-user as these complaints happen from time to time.
Diffstat (limited to 'discord/relationship.py')
0 files changed, 0 insertions, 0 deletions