| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | |/ / / / / / |
|
| | |\ \ \ \ \ \
| | |_|/ / / /
| |/| | | | | |
Show created date and duration in expired infraction log
|
| | | |\ \ \ \ \
| | |/ / / / /
| |/| | | | | |
|
| | | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
NGINX has been dockerised, and proxy passes now reference internal container domains rather than referencing host or external domains.
This will have a few extra benefits:
- Less external factors involved for resolving the service address
- Can work with the same address on development envs
- Snekbox can be closed down entirely so it's inaccessible from external networks.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The bot user was always being used instead of using the actor field
of the infraction.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes #685
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The absolute value is useful for preventing negative values in the case
that date_to is in the past relative to date_from.
* Add an absolute parameter to take the absolute value of the duration
* Rename expiry to date_to
* Rewrite the docstring
|
| | |\ \ \ \
| | |_|_|/
| |/| | | |
Stop scheduling expiration of permanent infractions on edit
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://github.com/python-discord/bot/issues/751
The infraction edit command defined in `bot.cogs.moderation.management` contained a bug causing it to attempt to schedule an expiration task when turning a temporary infraction into a permanent infraction. Since the "expires_at" field of a permanent infractions is `None`, this caused an exception to occur in the scheduler:
Traceback (most recent call last):
File "/bot/bot/cogs/moderation/scheduler.py", line 415, in _scheduled_task
expiry = dateutil.parser.isoparse(infraction["expires_at"]).replace(tzinfo=None)
File "/usr/local/lib/python3.7/site-packages/dateutil/parser/isoparser.py", line 37, in func
return f(self, str_in, *args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/dateutil/parser/isoparser.py", line 134, in isoparse
components, pos = self._parse_isodate(dt_str)
File "/usr/local/lib/python3.7/site-packages/dateutil/parser/isoparser.py", line 208, in _parse_isodate
return self._parse_isodate_common(dt_str)
File "/usr/local/lib/python3.7/site-packages/dateutil/parser/isoparser.py", line 213, in _parse_isodate_common
len_str = len(dt_str)
TypeError: object of type 'NoneType' has no len()
I have solved this by adding a check that makes sure we only schedule an expiration task when the `"expires_at"` field has a truthy value (which all valid datetime strings are) using `if request_data['expires_at']`.
IMPORTANT NOTE: While it's tempting to just skip the entire scheduling block for permanent infractions, it's essential to unschedule existing expiration tasks for this infraction as we're changing a temporary infraction to a permanent infraction.
This commit closes #751
|
| | | | | |
|
| | | | | |
|
| | | |\ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will prevent child classes to be instantiated unless they implement
all abstract methods, leading to a more descriptive error message.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will serve as an ABC for tests for individual rules.
The base class provides runners for allowed and disallowed
cases, and the children classes then only provide the cases
and implementations of helper methods specific to each rule.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The name msg is less descriptive and creates a needless name conflict in local gen exp.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The rule was incorrectly printing out the maximum amount of allowed attachments
instead of the configured interval. This commit also adjusts the rule's unit
test case.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
"Real" warnings weren't showing up for some reason.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
aiohttp does warn too, but these warnings will provide more immediate
feedback.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because discord.py recreates the HTTPClient session, may as well follow
suite and recreate our own stuff here too.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The function itself doesn't need to be a coroutine. It just has to be
called in a coroutine (or, more indirectly, in an async context?).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The client can be used without running a bot so it makes more sense
for the connector to be created when logging in, which is done in both
cases, rather than in start(), which is only used when running a bot.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
AsyncResolver has to be created inside a coroutine so it's moved
inside start(). Consequently, the APIClient session is also recreated
inside start() now.
When using clear(), the default connector is used for the session it
recreates because clear() is not a coroutine. This should only affect
requests made to the Discord API via the Client when not using it to run
a bot; starting the bot will re-create the session with the custom
connector.
* Close connector and resolver when bot closes
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These kwargs are merged with the kwargs given when the APIClient was
created. This is useful for facilitating changing the session's
connector with a new instance when the session needs to be recreated.
* Rename _session_args attribute to _default_session_kwargs
|
| |\ \ \ \
| | | | |
| | | | | |
Fix pagniation module for "last page" reaction
|
| |/ / / /
| | | |
| | | |
| | | | |
Fixes #746.
|
| |\ \ \ \
| | | | |
| | | | | |
Separate message/embed deletion and reaction deletion emojis
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It could be confused with the delete reaction. Clearing reactions
manually is rarely a useful feature anyway.
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Update discord.py to 1.3.1
|
| | | | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
Make it easier for user to search for tags
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Remove prometheus related code
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Move tools and questions guide to under resources
|
| | | | | | | | |
|