| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | | |
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
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
- Added new infraction delta calculations to updated infractions.
- Updates of infraction durations now also update the `last_applied` field.
- `inserted_at` is now sent by the bot client to denote the original unmodified infraction application time
|
| | | |
| | |
| | |
| | | |
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
|
| | | |
| | |
| | |
| | | |
Given API updates, the fallback is not needed
|
| | | |
| | |
| | |
| | | |
- Used arrow.utcnow to reduce complexity and import
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
- Added new usage of `last_applied` time for duration calculation in `apply_infraction`
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
- Corrected datetime patching
|
| | | |
| | |
| | |
| | | |
- Updated docstring to be more explicit on parameter fields
|
| | | |
| | |
| | |
| | | |
- Changed `duration` parameter names to `duration_or_expiry` to more accurately reflect options for help
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
- Refactored tests for new time duration arguments
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | | |
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.
|
| | | | |
| | | |
| | | |
| | | | |
Rather than passing around superfluous variables.
|
| | | | | |
|