aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Return False (not sent) at the end of display_tagGravatar F4zii2020-02-22-1/+1
| | | | | | If the code ran to the last line of the function without returning (we return when we send a tag) It means we didn't send the tag and need to return False
* awaited can_run CoroutineGravatar F4zii2020-02-22-1/+1
|
* Handling CommandError and OptimizationGravatar F4zii2020-02-22-6/+5
| | | | | | | After CommandError was catched, the embed was sent, now we return after the exception was catched Modified the way raw_commands are collected
* Only replace the misspelt command, and not the whole occurrences of itGravatar F4zii2020-02-21-1/+1
|
* Handling and logging CommandErrorGravatar F4zii2020-02-21-10/+14
| | | | | | | | the CommandError exception was ignored, We now catch the exception to handle and log the event Also added a little code reformat
* Command suggestion message reformat.Gravatar F4zi2020-02-20-2/+6
| | | | The message sent when suggesting a command is now wrapped inside an embed
* Rearrange - Function naming and DocstringsGravatar F4zii2020-02-20-105/+81
| | | | | | | | | get_command was changed to - display_tag, the name didn't fit, since its not the command itself. command_on_cooldown was taken out of display_tag to get the option to reuse it in another scope Docstrings modified
* Rearrange - Function naming and DocstringsGravatar F4zii2020-02-20-1/+1
|
* Return Logic FixedGravatar F4zii2020-02-19-2/+1
| | | | | | | The returned value was changed from True to False If we didn't return True (sent the tag) throughout the code It means we didn't send anything, we should return False
* Rearrange, NoneTypes handlingGravatar F4zii2020-02-19-3/+3
|
* Rearrange, Function naming and DocstringsGravatar F4zii2020-02-19-5/+16
|
* Rearrange, exception and NoneTypes handlingGravatar F4zii2020-02-19-12/+16
|
* Removal of unused logsGravatar F4zii2020-02-19-3/+0
|
* Suggest aliases when invoked instead of full command nameGravatar F4zii2020-02-19-3/+3
| | | | | | When found a similar command, the bot sent a suggestion about the full command name This was fixed by saving the matching alias and sending it instead of sending the full command name
* Delete_after added for suggestion messageGravatar F4zii2020-02-19-1/+2
| | | | preventing message spam by the bot when commands are misspelt
* Deletion of the consuming rest (*) used in _get_commandGravatar F4zii2020-02-19-2/+1
| | | | | Since its used to get the input of the command, its not needed again In the function (callback) call
*-. Merge branches 'feat/F4zi/CommandSuggestion' and 'master' of ↵Gravatar F4zii2020-02-19-17/+39
|\ \ | | | | | | | | | https://github.com/python-discord/bot into feat/F4zi/CommandSuggestion
| | * 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
| | | |\ | | | |/ | | |/|
| | | * 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
| * | | Merge branch 'master' into feat/F4zi/CommandSuggestionGravatar Matteo Bertucci2020-02-18-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.
* | | Feature: suggest command usage for misspelt commandsGravatar F4zii2020-02-19-4/+27
| | | | | | | | | | | | | | | | | | Migration to error_handler.py Suggesting misspelt commands, in progress
* | | Seperated tags.get_command into a function and a wrapperGravatar F4zii2020-02-19-23/+15
|/ / | | | | | | Updated
* / Feature: suggest command usage for misspelt commandsGravatar F4zii2020-02-18-0/+19
|/
* 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
| | | | |
| * | | | Merge branch 'master' into #549-show-attachments-staffGravatar Matteo Bertucci2020-02-03-508/+1333
| |\ \ \ \ | |/ / / / |/| | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-31 02:24:27 +0000