aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| * | | | | | Merge pull request #753Gravatar S. Co12020-02-19-16/+38
| |\ \ \ \ \ \ | | |_|/ / / / | |/| | | | | Show created date and duration in expired infraction log
| | * | | | | Merge branch 'master' into feat/frontend/b685/expired-infraction-log-durationGravatar S. Co12020-02-19-1/+1
| | |\ \ \ \ \ | | |/ / / / / | |/| | | | |
| * | | | | | Change snekbox api url to internal docker domain.Gravatar scragly2020-02-17-1/+1
| | |_|_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | | Moderation: show avatar in infraction deactivation logGravatar MarkKoz2020-02-19-0/+5
| | | | | |
| | * | | | Moderation: show member as a mention in expired infraction logGravatar MarkKoz2020-02-15-1/+1
| | | | | |
| | * | | | Moderation: show correct actor in expired infraction logGravatar MarkKoz2020-02-15-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bot user was always being used instead of using the actor field of the infraction.
| | * | | | Moderation: add creation date & duration to expired infraction logGravatar MarkKoz2020-02-15-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | Closes #685
| | * | | | Utils: refactor format_infraction_with_duration and support absolute valGravatar MarkKoz2020-02-15-13/+23
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | * | | Add unit test for newlines antispam ruleGravatar kwzrd2020-02-04-0/+105
| | | | |
| | * | | Add unit test for duplicates antispam ruleGravatar kwzrd2020-02-04-0/+66
| | | | |
| | * | | Merge branch 'master' into unittest-antispam-rulesGravatar Joseph2020-02-02-1/+10
| | |\ \ \
| | * | | | Make RuleTest use ABCMetaGravatar kwzrd2020-02-02-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will prevent child classes to be instantiated unless they implement all abstract methods, leading to a more descriptive error message.
| | * | | | Adjust existing tests to inherit from RuleTest ABCGravatar kwzrd2020-02-02-294/+157
| | | | | |
| | * | | | Implement RuleTest ABCGravatar kwzrd2020-02-02-0/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | | Adjust multi-line docstrings to prevailing styleGravatar kwzrd2020-01-31-3/+6
| | | | | |
| | * | | | Refactor msg helper function name to make_msgGravatar kwzrd2020-01-26-25/+25
| | | | | | | | | | | | | | | | | | | | | | | | The name msg is less descriptive and creates a needless name conflict in local gen exp.
| | * | | | Fix incorrect config key in attachments antispam ruleGravatar kwzrd2020-01-26-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | | Add unit test case for role mentions antispam ruleGravatar kwzrd2020-01-26-0/+66
| | | | | |
| | * | | | Add unit test case for discord emojis antispam ruleGravatar kwzrd2020-01-26-0/+68
| | | | | |
| | * | | | Add unit test case for chars antispam ruleGravatar kwzrd2020-01-26-0/+75
| | | | | |
| | * | | | Add unit test case for burst shared antispam ruleGravatar kwzrd2020-01-26-0/+65
| | | | | |
| | * | | | Add unit test case for burst antispam ruleGravatar kwzrd2020-01-26-0/+69
| | | | | |
* | | | | | Scheduler: make _scheduled_tasks privateGravatar MarkKoz2020-02-15-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Main concern is someone trying to cancel a task directly. The workaround for the race condition relies on the task only being cancelled via Scheduler.cancel_task(), particularly because it removes the task from the dictionary. The done callback will not remove from the dictionary if it sees the task has already been cancelled. So it's a bad idea to cancel tasks directly...
* | | | | | Moderation: avoid prematurely cancelling deactivation taskGravatar MarkKoz2020-02-15-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because deactivate_infraction() explicitly cancels the scheduled task, it now runs in a separate task to avoid prematurely cancelling itself.
* | | | | | Scheduler: cancel the task in the callbackGravatar MarkKoz2020-02-15-12/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This design makes more sense and is more convenient than requiring tasks to be responsible for cancelling themselves. * Rename _handle_task_exception to _task_done_callback * Add trace logging
* | | | | | Scheduler: raise task exceptions besides CancelledErrorGravatar MarkKoz2020-02-15-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Explicitly retrieves the task's exception, which will raise the exception if one exists. * Rename _suppress_cancelled_error to _handle_task_exception
* | | | | | Scheduler: remove loop parameter from schedule_taskGravatar MarkKoz2020-02-15-16/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | asyncio.create_task() exists and will already use the running loop in the current thread. Because there is no intention of using a different loop in a different thread anywhere in the program for the foreseeable future, the loop parameter is redundant.
* | | | | | Scheduler: correct schedule_task's docstringGravatar MarkKoz2020-02-15-1/+1
| | | | | |
* | | | | | Scheduler: remove create_task functionGravatar MarkKoz2020-02-15-15/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's redundant because the done callback only takes a single line to add and can be added in schedule_task(). * Use Task as the type hint rather than Future for _suppress_cancelled_error()
* | | | | | Scheduler: fix #754 - only suppress CancelledErrorGravatar MarkKoz2020-02-15-6/+7
|/ / / / /
* | | | | Merge pull request #752 from python-discord/infr-edit-permanent-fixGravatar Mark2020-02-14-2/+5
|\ \ \ \ \ | |_|_|_|/ |/| | | | Stop scheduling expiration of permanent infractions on edit
| * | | | Stop scheduling expiration of permanent infractions on editGravatar Sebastiaan Zeeff2020-02-14-2/+5
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge pull request #747 from mosguinz/pagniation-fixGravatar Sebastiaan Zeeff2020-02-12-1/+1
|\ \ \ \ | | | | | | | | | | Fix pagniation module for "last page" reaction
| * | | | Fix pagniation module for "last page" reactionGravatar mosguinz2020-02-12-1/+1
|/ / / / | | | | | | | | | | | | Fixes #746.
* | | | Merge pull request #625 from python-discord/emoji-cleanupGravatar Mark2020-02-09-14/+19
|\ \ \ \ | | | | | | | | | | Separate message/embed deletion and reaction deletion emojis
| * | | | Remove clear reaction from paginatorsGravatar MarkKoz2020-02-09-17/+2
| | | | | | | | | | | | | | | | | | | | | | | | | It could be confused with the delete reaction. Clearing reactions manually is rarely a useful feature anyway.
| * | | | Merge remote-tracking branch 'origin/master' into emoji-cleanupGravatar MarkKoz2020-02-08-2128/+4834
| |\ \ \ \ | |/ / / / |/| | | |
* | | | | Merge pull request #743 from python-discord/dep/b734/discord.py-1.3Gravatar Mark2020-02-07-39/+34
|\ \ \ \ \ | | | | | | | | | | | | Update discord.py to 1.3.1
| * | | | | Pin discord.py to 1.3.xGravatar MarkKoz2020-02-07-2/+2
| | | | | |
| * | | | | Update discord.py to 1.3.1Gravatar MarkKoz2020-02-07-39/+34
|/ / / / /
* | | | | Merge pull request #542 from python-discord/fuzzy-tag-searchGravatar Shirayuki Nekomata2020-02-07-9/+82
|\ \ \ \ \ | |_|_|_|/ |/| | | | Make it easier for user to search for tags
| * | | | Merge branch 'master' into fuzzy-tag-searchGravatar Matteo Bertucci2020-02-07-313/+199
| |\ \ \ \ | |/ / / / |/| | | |
* | | | | Merge pull request #737 from python-discord/remove-prometheusGravatar Mark2020-02-05-272/+128
|\ \ \ \ \ | | | | | | | | | | | | Remove prometheus related code
| * \ \ \ \ Merge branch 'master' into remove-prometheusGravatar S. Co12020-02-05-41/+71
| |\ \ \ \ \ | |/ / / / / |/| | | | |
* | | | | | Merge pull request #739 from python-discord/resources-moveGravatar Leon Sandøy2020-02-05-2/+2
|\ \ \ \ \ \ | | | | | | | | | | | | | | Move tools and questions guide to under resources
| * | | | | | Add missing slash to asking good questions url.Gravatar scragly2020-02-06-1/+1
| | | | | | |
| * | | | | | Move tools and questions guide to under resourcesGravatar scragly2020-02-05-2/+2
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | After the wiki pages adjustment to the resources page, these two urls are needing to be updated to point to the new correct locations for each page. Tools will be under resources, and Asking Good Questions is a guide, so will be under Guides.
* | | | | | Relay attachments to log channel before filters delete message (#630)Gravatar scragly2020-02-04-39/+69
|\ \ \ \ \ \ | |_|_|_|_|/ |/| | | | | Relay attachments to log channel before filters delete message
| * | | | | Use a trailing underscore to avoid name conflicts. Gravatar scragly2020-02-04-2/+2
| | | | | | | | | | | | | | | | | | Previously used a leading underscore, but that's usually meant for non-used names.
| * | | | | Change typehint name for the attachment-log constantGravatar Matteo Bertucci2020-02-03-1/+1
| | | | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-11 02:06:25 +0000