aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Incidents: make crawl limit & sleep module-level constantsGravatar kwzrd2020-06-20-10/+13
| | | | | | | Requested during review. Co-authored-by: ks129 <[email protected]> Co-authored-by: Joseph Banks <[email protected]>
* Incidents: make logs contain the message id they pertain toGravatar kwzrd2020-06-20-4/+4
| | | | | | Suggested by Mark during review. Co-authored-by: MarkKoz <[email protected]>
* Incidents: remove redundant `exc_info` passingGravatar kwzrd2020-06-20-4/+4
| | | | | | | | Pointed out by Mark during review that this is unnecessary, as logging using `exception` automatically appends the `exc_info` of the handled exception when done in an except block. Co-authored-by: MarkKoz <[email protected]>
* Incidents: reduce excessive whitespaceGravatar kwzrd2020-06-19-4/+1
| | | | | | | This is way too spacious for how little is happening here. Suggested by ks129. Co-authored-by: ks129 <[email protected]>
* Incidents: annotate possible None typeGravatar kwzrd2020-06-19-1/+1
| | | | | | Caught during review by ks129. Co-authored-by: ks129 <[email protected]>
* Incidents: remove broad noqaGravatar kwzrd2020-06-19-1/+1
| | | | | | | | | This was originally in place to silence a PyCharm warning regarding accessing the private attributes. However, since there is no corresponding error code to specify, the noqa will silence any linter warning, which is potentially dangerous, and seems to be bad practice.
* Incidents: review log levels; use `trace` where appropriateGravatar kwzrd2020-06-19-19/+19
| | | | | Logs useful when observing the internals but too verbose for DEBUG are reduced to TRACE.
* Incidents tests: write tests for `on_raw_reaction_add`Gravatar kwzrd2020-06-19-0/+128
|
* Incidents tests: write tests for `crawl_incidents`Gravatar kwzrd2020-06-19-0/+58
|
* Incidents tests: add helper for mocking async for-loopsGravatar kwzrd2020-06-19-0/+37
| | | | | | See the docstring. This does not make the ambition to be powerful enough to be included in `tests.helpers`, and is only intended for local purposes.
* Merge branch 'origin/master' into kwzrd/incidentsGravatar kwzrd2020-06-19-251/+643
|\
| * Merge pull request #892 from Akarys42/#364-offensive-msg-autodeletionGravatar Joseph Banks2020-06-17-9/+80
| |\ | | | | | | #364 offensive msg autodeletion
| | * Update deletion scheduler to use latest watchlist configurationGravatar Joseph Banks2020-06-17-17/+5
| | |
| | * Merge branch 'master' into #364-offensive-msg-autodeletionGravatar Joseph Banks2020-06-17-2517/+7259
| | |\ | | |/ | |/|
| * | Merge pull request #991 from crazygmr101/feature/cooldown-tagGravatar Mark2020-06-17-0/+20
| |\ \ | | | | | | | | Create cooldown.md
| | * | Update bot/resources/tags/customcooldown.mdGravatar Daniel Nash2020-06-15-3/+1
| | | | | | | | | | | | Co-authored-by: Mark <[email protected]>
| | * | Merge branch 'master' into feature/cooldown-tagGravatar Joseph Banks2020-06-12-76/+179
| | |\ \
| | * | | Add scheme to URLGravatar Daniel Nash2020-06-12-1/+1
| | | | |
| | * | | Update customcooldown.mdGravatar Daniel Nash2020-06-12-0/+2
| | | | |
| | * | | Make title more specificGravatar Daniel Nash2020-06-12-1/+1
| | | | | | | | | | | | | | | Co-authored-by: Mark <[email protected]>
| | * | | Update bot/resources/tags/customcooldown.mdGravatar Daniel Nash2020-06-10-3/+1
| | | | | | | | | | | | | | | Co-authored-by: Joseph Banks <[email protected]>
| | * | | change _cd to message_cooldown Gravatar Daniel Nash2020-06-10-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Apply suggestions from code review Co-authored-by: Joseph Banks <[email protected]>
| | * | | Move the not rate-limited message into elseGravatar Daniel Nash2020-06-10-1/+3
| | | | |
| | * | | Update example to not be in a cogGravatar Daniel Nash2020-06-10-12/+10
| | | | |
| | * | | Rename to customcooldown.mdGravatar Daniel Nash2020-06-10-0/+0
| | | | |
| | * | | Update cooldown.mdGravatar Daniel Nash2020-06-07-1/+1
| | | | |
| | * | | Create cooldown.mdGravatar Daniel Nash2020-06-07-0/+22
| | | | |
| * | | | Merge pull request #1001 from python-discord/bug/mod/bot-68/ban-strips-noneGravatar Mark2020-06-17-22/+38
| |\ \ \ \ | | | | | | | | | | | | Check infraction reason isn't None before shortening it
| | * | | | Format parameters with a more consistent styleGravatar MarkKoz2020-06-16-19/+19
| | | | | |
| | * | | | Add optional type annotations to reason in pardon funcsGravatar MarkKoz2020-06-16-2/+2
| | | | | |
| | * | | | Revise inaccurate typehint for Optional reasonGravatar kosayoda2020-06-16-18/+31
| | | | | |
| | * | | | Fix check for bot actor in infractionsGravatar MarkKoz2020-06-14-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The reason None check should be nested to avoid affecting the else/elif statements that follow.
| | * | | | Check infraction reason isn't None before shortening itGravatar MarkKoz2020-06-14-5/+8
| | | | | |
| * | | | | Add LMGTFY to domain blacklistGravatar Joseph Banks2020-06-17-0/+1
| | | | | |
| * | | | | Merge pull request #987 from python-discord/help_channel_rediscacheGravatar Kieran Siek2020-06-16-53/+98
| |\ \ \ \ \ | | | | | | | | | | | | | | Add persistence to the help channel system
| | * \ \ \ \ Merge branch 'master' into help_channel_rediscacheGravatar Kieran Siek2020-06-16-243/+585
| | |\ \ \ \ \ | | |/ / / / / | |/| | | | |
| * | | | | | Log exception info for failed attachment uploadsGravatar MarkKoz2020-06-15-1/+1
| | |/ / / / | |/| | | |
| * | | | | Add the C# guild to the whitelistGravatar Dennis Pham2020-06-15-0/+1
| | | | | |
| * | | | | Merge pull request #937 from python-discord/bug/filters/928/non-ascii-tokenGravatar Mark2020-06-12-154/+357
| |\ \ \ \ \ | | | | | | | | | | | | | | Make token detection more robust and completely rewrite its tests
| | * \ \ \ \ Merge remote-tracking branch 'origin/master' into ↵Gravatar MarkKoz2020-06-02-1044/+2456
| | |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | bug/filters/928/non-ascii-token
| | * | | | | | Token remover: remove the `delete_message` functionGravatar MarkKoz2020-06-02-19/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's redundant; there's no benefit here in abstracting two lines of code into a function.
| | * | | | | | Test find_token_in_message returns None for invalid matchesGravatar MarkKoz2020-05-28-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This covers the case when a token is matched, but its user ID and timestamp turn out to be invalid.
| | * | | | | | Adjust find_token_in_message tests for the recent cog changesGravatar MarkKoz2020-05-28-19/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It now supports the changes that switched to finditer, added match groups, and added the Token NamedTuple. It also accounts for the is_maybe_token function being removed. For the sake of simplicity, call assertions on is_valid_user_id and is_valid_timestamp were not made.
| | * | | | | | Remove is_maybe_token testsGravatar MarkKoz2020-05-28-33/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function was removed due to redundancy. Therefore, its tests are obsolete.
| | * | | | | | Add more thorough and realistic inputs for token ID and timestamp testsGravatar MarkKoz2020-05-27-18/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tests for valid inputs and invalid inputs were split to make them more readable.
| | * | | | | | Adjust token remover tests to use the Token NamedTupleGravatar MarkKoz2020-05-27-6/+8
| | | | | | | |
| | * | | | | | Switch findall to finditer in assertionsGravatar MarkKoz2020-05-27-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `find_token_in_message` now uses the latter so the tests should adjust accordingly.
| | * | | | | | Use real token values for testing multiple matches in regexGravatar MarkKoz2020-05-25-3/+4
| | | | | | | |
| | * | | | | | Fix multiple match text for token regexGravatar MarkKoz2020-05-25-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It has to account for the addition of groups. It's easiest to compare the entire string so `finditer` is used to return re.Match objects; the tuples of `findall` would be cumbersome. Also threw in a change to use `assertCountEqual` cause the order doesn't really matter.
| | * | | | | | Fix valid token regex testGravatar MarkKoz2020-05-25-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was broken due to the addition of groups. Rather than returning the full match, `findall` returns groups if any exist. The test was comparing a tuple of groups to the token string, which was of course failing. Now `fullmatch` is used cause it's simpler - just check for `None` and don't worry about iterating matches to search.
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-27 07:05:41 +0000