| Commit message (Collapse) | Author | Age | Lines |
| |\
| |
| | |
feat: add reason argument to pardon commands
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Correctly initialise redis tests
|
| |/
|
|
|
|
|
|
|
| |
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]>
|
| |\
| |
| | |
Globally decode binary responses from redis to strings
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
The new versions introduce conversions which causes the doc command
embed to be formatted improperly
|
| | | |
|
| | |
| |
| |
| | |
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 was a new lint rule added in the latest bugbear.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
If a float is given, Redis will assume the expiry is in milliseconds and must be multiplied by 1000. This is undesirable, as we are already passing the expiry in seconds.
|
| | | |
|
| | |
| |
| |
| | |
This has been abstracted away, the correct way to do this now is to directly access the client.
|
| | |
| |
| |
| | |
This commit resolves all the breaking changes from the aioredis -> redis-py migration.
|
| | | |
|
| | |
| |
| |
| | |
This bump comes with a move to redis-py over aioredis. As such, pin new transitive dependancies to exact versions.
|
| | |
| |
| |
| | |
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 bot service was still configured to depend on the snekbox service, even though this service is now optional, in favour of the snekbox-311 service.
|
| |\
| |
| | |
Updated `purge` to require at least one user
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
feat(tags): add print-return tag
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Update `!modpings off` confirmation to use a discord timestamp.
|
| | |\ \
| |/ /
|/| | |
|
| | | | |
|
| | | |\
| |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
Use the view clear on timeout feature from bot-core in snekbox
|
| | | | |
| | | |
| | | |
| | | | |
Since snekbox uses 3.11 by default, it makes sense for this one to be started by default, and the 3.10 container to be opt-in.
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | | |
This will mean the buttons will be cleared from the response on interaction timeout.
|
| | | |
| | |
| | |
| | |
| | | |
As mentioned in the previous commit, using the raw GitHub URL would be
more reliable than a Discord CDN URL.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
As discussed in
https://discord.com/channels/267624335836053506/635950537262759947/998235482494353508,
using the raw GitHub URL for the GIF would be more reliable than the
Discord CDN URL.
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| | |
Since we already create the tag embed from the `embed` object in the metadata, we already have the
support to add images in embeds, albeit a bit more verbose than if we had added a `media` property
in the metadata containing only the URL.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This is so that we do not need to spawn the run_job call in a seperate task.
This also wraps interaction.message.delete() in a NotFound suppress to cover the case where a user re-runs code and very quickly clicks the button. The log arg on send_job will stop the actual job from running in this case.
|
| | | |
| | |
| | |
| | | |
The cog_command_error isn't hit when the run_job function is called from the button interaction, this means if the lock error is raiseed, it doees not get handled.
|