-
Notifications
You must be signed in to change notification settings - Fork 15
Avoid fetching or relying on guild member info #37
Copy link
Copy link
Open
Labels
bugscope:mediumBug affects some users and minor features, but no core functionalityBug affects some users and minor features, but no core functionalitydifficulty:mediumLocal knowledge needed of relevant modules and librariesLocal knowledge needed of relevant modules and librariesmodule:registrySession data storage, access, or analysisSession data storage, access, or analysismodule:timer-coreTimer module core functionality (timers, subscribers, timerchannels, etc)Timer module core functionality (timers, subscribers, timerchannels, etc)module:timer-interfaceClient to timer interfaceClient to timer interface
Description
Metadata
Metadata
Assignees
Labels
bugscope:mediumBug affects some users and minor features, but no core functionalityBug affects some users and minor features, but no core functionalitydifficulty:mediumLocal knowledge needed of relevant modules and librariesLocal knowledge needed of relevant modules and librariesmodule:registrySession data storage, access, or analysisSession data storage, access, or analysismodule:timer-coreTimer module core functionality (timers, subscribers, timerchannels, etc)Timer module core functionality (timers, subscribers, timerchannels, etc)module:timer-interfaceClient to timer interfaceClient to timer interface
Issues
Due to recent discord API changes, the member cache is usually non-existent, and
guild.get_member()will usually returnNone.This is used, in particular, while loading timer subscribers from session data, resulting in no subscribers being loaded.
Proposed solution
Avoid using
memberobjects wherever possible, relying solely on the user id.