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
If a webhook returns an error such as a 429 error, there should be a way to iterate through the supplied dict of proxies.
As far as I'm aware, setting the proxies for a webhook object does not persist through a While or For-loop if it is nested. As such, proxies (to my albeit mediocre coding skills) can't be changed per n messages sent.
The proxies used by the webhook should be an attribute of the webhook so debugging for proxy usage is easier.
The text was updated successfully, but these errors were encountered:
Could you iterate through the webhook.proxies attribute of a given webhook that you call .execute() on?
The workaround is a little hacky, but you could modify the .proxies attribute of the webhook object in the for/while loop, given that the webhook object persists, a.k.a. initializing it before entering the loop.
As for you third point, the proxies are available with webhook.proxies, that's where the DiscordWebhook class stores them the proxies to use, until and after executed.
Does this help? And if not, do you have any subsequent questions?
If a webhook returns an error such as a 429 error, there should be a way to iterate through the supplied dict of proxies.
As far as I'm aware, setting the proxies for a webhook object does not persist through a While or For-loop if it is nested. As such, proxies (to my albeit mediocre coding skills) can't be changed per n messages sent.
The proxies used by the webhook should be an attribute of the webhook so debugging for proxy usage is easier.
The text was updated successfully, but these errors were encountered: