Closed RobPando closed 1 year ago
I also saw this error personally. I was under the memory that we added a clause to handle it because we couldn't figure out the source, but I'm not sure where it went right now :thinking:
@RobPando Can you try again from the latest master? We have updated the gun
dependency used for requests and in the patch notes some fixes for spurious errors were mentioned.
I have been getting the error
no function clause matching in Nostrum.Api.Ratelimiter.handle_info/2
for:gun_error
from time to time for a few months now, they do not happen often and I am not sure what triggers it but I cannot ignore it anymore. I realized the module does not have this matching and I am wondering if I am missing something, not sure if it is helpful but the only function I am utilizing from the package isNostrum.Api.create_message
so this must be triggering from that. Thank you for the help in advance.