| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Use the more concise DATETIME timestamp instead of both a DATE and a TIME timestamp.
- Remove underline from the "Reported ..." section at the bottom of the embed.
- Re-add time of action/rejection timestamp to footer of embed.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Corrected test case to use `datetime.utcnow()` to be consistent with target
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Used new method of dict subset comparison instead of datetime patching for better compat. with argument types
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Corrected datetime patching
|
| | | | | | | |
|
| | | | | | | |
|
| | | | |_|/
| | |/| |
| | | | |
| | | | | |
- Refactored tests for new time duration arguments
|
| | | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Calling the cog_load from within the setUp function resulted in interaction with a RedisSession before it was initialised.
This wasn't noticed in CI as it only error under certain concurrency timings due to xdist.
To resolve this, we moved the setup and async setup logic to a base class.
Co-authored-by: Hassan Abouelela <[email protected]>
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This helper ensures that a fresh RedisSession is given to each test case that inherits from it.
|
| | | | |
| | | |
| | | |
| | | | |
pep-naming now supports these functions being in camel case.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This has been abstracted away, the correct way to do this now is to directly access the client.
|
| | | | |
| | | |
| | | |
| | | | |
These warnings were caused by the setup coro from error_handler.py being imported directly, causing a warning about an un-awaited coro whenever the Cog was accessed from the same file.
|
| | | | |
| | | |
| | | |
| | | | |
get_event_loop is deprecated as of 3.10 if there is no running loop.
|
| | |/ / |
|
| | | | |
|
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The user syncer was blocking the startup of the sync cog due to having
to perform thousands of pointless member fetch requests. This speeds up
that process by increasing the probability that the cache is up-to-date
using `Guild.chunked`, and limiting the fetches to members who were in
the guild during the previous sync only.
Co-authored-by: ChrisJL <[email protected]>
Co-authored-by: wookie184 <[email protected]>
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Discord.py now implicitly calls the new async cog_load function from within it's internals on load. There is no longer a need to test that this happens.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
region was removed from the guild object, so this has been replaced with features
add_cog is now async, so it is now an async_mock during tests
Two new required voice_channel attrs were added
channel.type is required to be set to ChannelType due to a new isinstance check in d.py
|
| | | |
|
| | |
| |
| |
| | |
We now source them from bot-core, so no need to have them here too.
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
This reverts commit 960619c23300c56c8aaa454edc7241e2badf80ad.
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | | |
All of the tag content is out of scope for this PR.
|
| | |\| | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: GDWR <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: GDWR <[email protected]>
|