Closed aguxez closed 7 years ago
ATM the cache doesn't automatically load up offline members, so it's possible that an invisible user triggering this command wouldn't be present in the cache. It's also possible that connection issues cause the cache to not be fully loaded when the command gets triggered, thus leading to the same thing.
This could be "solved" by doing an API request, but I don't like the idea of hitting the api inside of these macros.
The fact that Cogs.member
returns an error tuple does warn about the eventual possibility of failure,
so I don't really consider this to be an issue.
When I try to get a member information through the member macro in Cogs I get an error saying that It failed to find an entry for {member id}, it some times work and some times it doesnt, I'm pattern matching the results of
Cogs.member
and when I try to inspect it, it may work or it may not and I have not changed anything in the code while testing this ^^, this is the traceback:This is the only thing I have on the code so, uh, nothing crazy...
A thought came in my mind about a rate limit but I don't think that's the error it would be displaying.