aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| | * | | | | | | ModLog: ignore DMs in the message delete listenerGravatar MarkKoz2020-05-10-0/+4
| | | | | | | | |
| | | * | | | | | Add snekbox to the Docker compose fileGravatar MarkKoz2020-06-05-0/+9
| | | | | | | | |
| | | | * | | | | Fix exception message assertions in converter testsGravatar MarkKoz2020-04-28-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `msg` arg is for displaying a message when the assertion fails. To match against the exception's message, `assertRaisesRegex` must be used. Since all of the messages are meant to be interpreted literally rather than as regex, `re.escape` is used.
| | | | * | | | | Use await instead of asyncio.run in converter testsGravatar MarkKoz2020-04-28-28/+27
| | | | | | | | |
| | | | * | | | | Remove redundant parenthesis from test valuesGravatar MarkKoz2020-04-28-19/+19
| | | | | | | | |
| | | | * | | | | Test for out of range datetime in the Duration converterGravatar MarkKoz2020-04-28-0/+11
| | | | | | | | |
| | | | * | | | | Converters: handle ValueError when year for duration is out of rangeGravatar MarkKoz2020-04-25-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `datetime` objects only support a year up to 9999. Fixes #906
| | | | | * | | | Filtering: Add user avatar thumbnail to nickname alert embedGravatar ks1292020-06-11-1/+2
| | | | | | | | |
| | | | | * | | | Filtering: Use walrus for better looking of codeGravatar ks1292020-06-11-4/+2
| | | | | | | | |
| | | | | * | | | Filtering: Fix nickname filter alert sending spacesGravatar ks1292020-06-11-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Co-authored-by: Joseph Banks <[email protected]>
| | | | | * | | | Filtering: Fix some commentsGravatar ks1292020-06-11-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Co-authored-by: Joseph Banks <[email protected]>
| | | | | * | | | Remove redis namespace collision testGravatar MarkKoz2020-05-31-10/+0
| | | | | | | | |
| | | | | * | | | Remove redis namespace collision preventionGravatar MarkKoz2020-05-31-10/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When cogs reload, it would consider their namespace as a conflict with the original namespace. This feature will be removed as a fix until we come up with a better solution.
| | | | | * | | | Add logging for the bad nickname filterGravatar MarkKoz2020-05-31-0/+2
| | | | | | | | |
| | | | | * | | | Fix missing await in bad nickname filterGravatar MarkKoz2020-05-31-18/+17
| | | | | | | | |
| | | | | * | | | Filtering: Small fixesGravatar ks1292020-05-31-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Use UTC from timestamp - Rename name bad words checking function
| | | | | * | | | Filtering: Fix docstringGravatar ks1292020-05-31-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Co-authored-by: Mark <[email protected]>
| | | | | * | | | Merge remote-tracking branch 'origin/bad-words-nick' into bad-words-nickGravatar ks1292020-05-31-4/+1
| | | | | |\ \ \ \
| | | | | | * | | | Filtering: Create lock in `__init__`Gravatar ks1292020-05-30-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move lock creation from `bad_words_in_name` to `__init__`
| | | | | * | | | | Filtering: Split name filtering to smaller functionsGravatar ks1292020-05-31-11/+24
| | | | | | | | | |
| | | | | * | | | | Filtering: On name filtering, replace Message with Embed as argumentGravatar ks1292020-05-31-7/+7
| | | | | | | | | |
| | | | | * | | | | Filtering: Add days between alerts as constantGravatar ks1292020-05-31-1/+3
| | | | | | | | | |
| | | | | * | | | | Filtering: Rename `bad_words_in_name` to `check_is_bad_words_in_name`Gravatar ks1292020-05-31-2/+2
| | | | | | | | | |
| | | | | * | | | | Filtering: Use POSIX instead ISO format to storage alert cooldownsGravatar ks1292020-05-31-3/+2
| | | | | |/ / / /
| | | | | * | | | Filtering: Refactor bad names checkingGravatar ks1292020-05-29-31/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Make `bad_words_in_name` and attach it to current `on_message`. - Implement `asyncio.Lock` to avoid race conditions. - Made that this first check is there matches and when there is, check for alert.
| | | | | * | | | Filtering: Implement bad words detection in nicknamesGravatar ks1292020-05-29-0/+41
| | | | | | | | |
| | | | | | | | * Revise inaccurate docstring in RedisCacheGravatar kosayoda2020-06-16-2/+2
| | | | | | | | |
| | | | | | | | * Refactor nested if-statementGravatar kosayoda2020-06-16-5/+4
| | | | | | | | |
| | | | | | | | * Help channels: revise inaccurate commentGravatar MarkKoz2020-06-08-1/+1
| | | | | | | | |
| | | | | | | | * Help channels: use cache to remove cooldowns or re-schedule themGravatar MarkKoz2020-06-08-7/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Using the cache is more efficient since it can check only the users it expects to have a cooldown rather than searching all guild members. Furthermore, re-scheduling the cooldowns ensures members experience the full duration of the cooldown. Previously, all cooldowns were removed, regardless of whether they were expired.
| | | | | | | | * Help channels: add a function to schedule cooldown expirationGravatar MarkKoz2020-06-08-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moving this code into a separate function reduces redundancy down the line. This will also get used to re-scheduled cooldowns after a restart.
| | | | | | | | * Help channels: add a function to get in use timeGravatar MarkKoz2020-06-08-5/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Future code will also need to get this time, so moving it out to a separate function reduces redundancy.
| | | | | | | | * Help channels: fix claim timestamp being localGravatar MarkKoz2020-06-08-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The datetime module returns a local timestamp for naïve datetimes. It has to be timezone-aware to ensure it will always be in UTC.
| | | | | | | | * Remove pointless suppress.Gravatar Leon Sandøy2020-06-07-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since help_channel_claimants.delete will never raise a KeyError, it's not necessary to suppress one.
| | | | | | | | * Merge branch 'master' into help_channel_rediscacheGravatar Leon Sandøy2020-06-06-1/+7
| | | | | | | | |\ | |_|_|_|_|_|_|_|/ |/| | | | | | | |
* | | | | | | | | Enable the 'redis' / 'aiohttp' Sentry integrationsGravatar Leon Sandøy2020-06-06-1/+7
| |_|/ / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will provide breadcrumbs for these systems in all our Sentry events, if applicable. Closes #989.
| | | | | | | * Merge branch 'master' into help_channel_rediscacheGravatar Leon Sandøy2020-06-06-84/+134
| | | | | | | |\ | |_|_|_|_|_|_|/ |/| | | | | | |
* | | | | | | | Merge pull request #985 from ks129/rules-statsGravatar kwzrd2020-06-06-0/+3
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | Stats: Implement rules stats
| * \ \ \ \ \ \ \ Merge branch 'master' into rules-statsGravatar kwzrd2020-06-06-185/+460
| |\ \ \ \ \ \ \ \ | |/ / / / / / / / |/| | | | | | | |
* | | | | | | | | Merge pull request #970 from python-discord/staff_count_serverGravatar kwzrd2020-06-05-12/+65
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | Add staff counts to !server
| * \ \ \ \ \ \ \ \ Merge branch 'master' into staff_count_serverGravatar kwzrd2020-06-05-72/+66
| |\ \ \ \ \ \ \ \ \ | |/ / / / / / / / / |/| | | | | | | | |
* | | | | | | | | | Merge pull request #984 from ↵Gravatar Joseph Banks2020-06-05-20/+21
|\ \ \ \ \ \ \ \ \ \ | |_|_|/ / / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | python-discord/sebastiaan/issues/982-infraction-dm-order Send infraction DM before applying infraction
| * | | | | | | | | Send infraction DM before applying infractionGravatar Sebastiaan Zeeff2020-06-05-20/+21
|/ / / / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've "reverted" the change that reversed the order of DM'ing a user about their infraction and applying the actual infraction. A recent PR reversed the order to stop us from sending DMs when applying the infraction failed. However, in order to DM a user, the bot has to share a guild with the recipient and kicking them off of our server first does not help with that. That's why I reverted the change and reverted some other minor changes made in relation to this change. Note: I did not change the code sending the DM itself; I merely moved it back to where it belongs and added a comment about the necessity of doing the DM'ing first. I couldn't cleanly revert a commit to do this, as changes were spread out over and included in multiple commits that also contained changes not related to the `DM->apply infraction` order.
* | | | | | | | | Merge pull request #979 from neonsea/modmail-tagGravatar Dennis Pham2020-06-02-0/+9
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | Add the !modmail tag
| * | | | | | | | | add modmail tagGravatar Rasmus Moorats2020-06-02-0/+9
|/ / / / / / / / /
* | | | | | | | | Merge pull request #962 from python-discord/stop_sending_avatar_hashGravatar Sebastiaan Zeeff2020-06-02-11/+2
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | Remove all sending of avatar_hash
| * \ \ \ \ \ \ \ \ Merge branch 'master' into stop_sending_avatar_hashGravatar Sebastiaan Zeeff2020-06-02-41/+34
| |\ \ \ \ \ \ \ \ \ | |/ / / / / / / / / |/| | | | | | | | |
* | | | | | | | | | Merge pull request #974 from python-discord/multichannel_purgeGravatar Dennis Pham2020-05-31-41/+34
|\ \ \ \ \ \ \ \ \ \ | |_|_|_|_|_|_|/ / / |/| | | | | | | | | Add multichannel !purge
| * | | | | | | | | Use the messages returned by `purge` to upload message logsGravatar MarkKoz2020-05-31-7/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This ensures that only what was actually deleted will be uploaded. I managed to get a 400 response from our API when purging twice in quick succession. Searching the history manually for these messages is unreliable cause of some sort of race condition.
| * | | | | | | | | Revert message ignore approach.Gravatar Leon Sandøy2020-05-31-10/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We're removing the context manager due to async concerns, so we'll go back to the old approach again of ignoring specific messages and iterating history.