aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Incidents tests: create new test moduleGravatar kwzrd2020-06-12-0/+0
|
* Merge branch 'origin/master' into kwzrd/incidentsGravatar kwzrd2020-06-12-22/+62
|\
| * Replace mention of Flask with DjangoGravatar Mark2020-06-11-1/+1
| | | | | | | | The site's description still stated that it was built with Flask, which is no longer accurate due to the move to Django.
| * Merge pull request #964 from ks129/bad-words-nickGravatar Joseph Banks2020-06-11-21/+61
| |\ | | | | | | Filtering: Implement bad words detection in nicknames
| | * Merge branch 'master' into bad-words-nickGravatar Joseph Banks2020-06-11-1/+35
| | |\ | | |/ | |/|
| | * Merge branch 'master' into bad-words-nickGravatar ks1292020-06-11-239/+552
| | |\
| | * | 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
| | | |
* | | | Incidents: extend documentationGravatar kwzrd2020-06-12-11/+49
| | | | | | | | | | | | | | | | | | | | This adds a proper class docstring & small touch-ups to local comments where necessary.
* | | | Incidents: avoid lambda check; make regular functionGravatar kwzrd2020-06-12-5/+5
| | | |
* | | | Incidents: log `event_lock` releaseGravatar kwzrd2020-06-12-0/+1
| | | |
* | | | Incidents: do not process reaction events from botsGravatar kwzrd2020-06-12-2/+3
| | | |
* | | | Incidents: implement `process_event` coroutineGravatar kwzrd2020-06-12-3/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This contains the main logic for handling reactions and glues all the helpers together. Unfortunately, gracefully handling everything that can go wrong in the process requires quite a lot of code ~ but, at least to me, it seems like this all should now be fairly safe. The idea to await the message delete event before releasing the lock was conceived by Ves, while Mark helped me refine it. Co-authored-by: Sebastiaan Zeeff <[email protected]> Co-authored-by: MarkKoz <[email protected]>
* | | | Incidents: implement `make_confirmation_task` methodGravatar kwzrd2020-06-12-0/+15
| | | |
* | | | Incidents: implement `archive` methodGravatar kwzrd2020-06-12-1/+39
| | | |
* | | | Incidents: implement reaction listenerGravatar kwzrd2020-06-12-0/+46
| | | | | | | | | | | | | | | | See docstring!
* | | | Incidents: implement `resolve_message`Gravatar kwzrd2020-06-12-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | See docstring. The exception log is DEBUG level as failure does not necessarily indicate that we have done something wrong. We rely on the API to tell us that the message no longer exists in situations where we have 2 coroutines racing to archive the same message.
* | | | Incidents: make `crawl_incidents` smarterGravatar kwzrd2020-06-12-6/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The crawler now avoids making API calls for messages which: * Are not incidents * Already have all signals As a result, we can sleep only after making actual calls. This speeds up the task completion considerable, while also making it lighter on the API. Victory!
* | | | Incidents: move `add_signals` to module namespaceGravatar kwzrd2020-06-12-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Looks like we'll need quite a few helpers, and I think it's cleaner to keep them at module level. It helps avoid the question of: what do I do if a staticmethod depends on another staticmethod?
* | | | Incidents: implement `has_signals` helperGravatar kwzrd2020-06-12-0/+6
| | | |
* | | | Incidents: implement `own_reactions` helperGravatar kwzrd2020-06-12-1/+6
| | | |
* | | | Incidents: abstract incident checking into a helper methodGravatar kwzrd2020-06-12-24/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code is now basically self-documenting, the docstring is no longer necessary. The ultimate goal is to allow `crawl_incidents` to be more smart about which messages need to be passed to `add_signals`, so that it doesn't need to sleep after each message.
* | | | Incidents: add `event_lock` for simple event synchronizationGravatar kwzrd2020-06-12-1/+3
| | | |
* | | | Incidents: only `add_signals` if missingGravatar kwzrd2020-06-12-2/+10
| | | |
* | | | Incidents: make `on_message` ignore pinned messagesGravatar kwzrd2020-06-12-0/+5
| | | | | | | | | | | | | | | | | | | | This is now necessary as we call the listener ourselves from the crawl task. An already existing, pinned message, can be received.
* | | | Incidents: implement & schedule `crawl_incidents` taskGravatar kwzrd2020-06-12-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See docstring for further information. This will run on start-up to retroactively add missing emoji. Ratelimit-wise this should be fine, as there should never be too many missing emoji.
* | | | Incidents: implement `on_message` listener & guardsGravatar kwzrd2020-06-12-3/+20
| | | |
* | | | Incidents: implement `add_signals` helperGravatar kwzrd2020-06-12-2/+6
| | | | | | | | | | | | | | | | Looks like it can be static, at least for now.
* | | | Incidents: define method stubs for message event handlingGravatar kwzrd2020-06-12-0/+10
| | | |
* | | | Incidents: define allowed roles and emojiGravatar kwzrd2020-06-11-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | These serve as whitelists, i.e. any reaction using an emoji not explicitly allowed, or from a user not specifically allowed, will be rejected. Such reactions will be removed by the bot.
* | | | Merge branch 'origin/master' into kwzrd/incidentsGravatar kwzrd2020-06-11-53/+115
|\| | |
| * | | Merge pull request #995 from python-discord/add-cooldown-channelGravatar Mark2020-06-11-1/+3
| |\ \ \ | | | | | | | | | | Add cooldown channel to config-default.yml
| | * | | Add cooldown to Channels in constants.pyGravatar Joseph Banks2020-06-11-0/+1
| | | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-24 13:49:04 +0000