Skip to content
This repository has been archived by the owner. It is now read-only.

Pruning on mega-guilds #2085

Closed
Kowlin opened this issue Apr 14, 2019 · 0 comments
Closed

Pruning on mega-guilds #2085

Kowlin opened this issue Apr 14, 2019 · 0 comments
Labels
Milestone

Comments

@Kowlin
Copy link
Contributor

@Kowlin Kowlin commented Apr 14, 2019

Summary

I'll be referencing mega-guilds a lot here in this issue, so for our sake consider a mega-guild on Discord a guild with over 200K members.

There currently exists an issue on Discord whereby pruning on mega-guilds will take to long that the endpoint will often fail to respond at all, but the prune will still be initiated. This will occur for both the functions client.estimate_pruned_members and client.prune_members Discord has addressed this with a new field on the prune endpoint. (docs) Which will return None on the number of members pruned immediately and start the prune.

However, without the use of compute_prune_count=False the response from Discord will take long enough that the bot will try and initiate another prune until it reaches it maximum retries.

Reproduction Steps

  1. Initiate a prune on a mega-guild
  2. Discord will not return a response in time
  3. The bot will retry to start a prune while in reality one is already on going.

System Information

  • discord.py version: Any version of rewrite
  • Python version: 3.7
  • Operating system: Linux Ubuntu 18.04 LTS
@Rapptz Rapptz closed this in 519f0c0 Apr 14, 2019
@Rapptz Rapptz added the bug label May 10, 2019
@Rapptz Rapptz added this to the v1.1 milestone May 10, 2019
yagomichalak pushed a commit to yagomichalak/discord.py that referenced this issue May 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants