| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / / |
|
| | | | |/
| | | |
| | | |
| | | |
| | | | |
- Convert `ids` to a set to remove duplicates
- Limit the amount of reminders you can delete at once to 5 in order to prevent API spam
|
| | | | | |
|
| | | |/
| |/| |
|
| | |\ \
| | | |
| | | | |
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.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
To do this we need to track, for each user, the active eval's code, python version and response message. This is because a button press can now also trigger a job to continue. If we did not track these, then editing your own code and then re-evaluating it would trigger the wait_fors in continue_job for each time you pressed the button to change languages.
Co-authored-by: Mark <[email protected]>
|
| | |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In order to facilitate this change, the init of all setting entries was removed, and as such the base SettingsEntry class doesn't count as abstract anymore, which broke the MUST_SET behavior. It was changed to not raise errors for MUST_SET values of attributes which were set in the current class.
Additionally fixed a small bug where filters weren't listed properly in the list command.
Despite the pydantic manual not writing it that way, I first made the validators class methods, otherwise it gave linting errors which couldn't be ignored with noqa (because then it complained about blanket noqas).
|