aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* 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
| | |
| | * Add cooldown channel to EXCLUDED_CHANNELS tupleGravatar Joseph Banks2020-06-11-1/+1
| | |
| | * Add cooldown channel to config-default.ymlGravatar Joseph Banks2020-06-11-0/+1
| |/
| * Fix trailing whitespace in Action fileGravatar Joseph Banks2020-06-11-1/+1
| |
| * Create codeql-analysis.ymlGravatar Joseph Banks2020-06-11-0/+32
| |
| * Merge pull request #910 from python-discord/bug/backend/906/converter-year-rangeGravatar Joseph Banks2020-06-10-52/+66
| |\ | | | | | | Converters: handle ValueError when year for duration is out of range
| | * Merge branch 'master' into bug/backend/906/converter-year-rangeGravatar Joseph Banks2020-06-10-1194/+2938
| | |\ | | |/ | |/|
| * | Merge pull request #988 from python-discord/snekbox-composeGravatar Joseph Banks2020-06-10-0/+9
| |\ \ | | | | | | | | Add snekbox to the Docker compose file
| | * \ Merge branch 'master' into snekbox-composeGravatar Joseph Banks2020-06-10-2/+14
| | |\ \ | | |/ / | |/| |
| * | | Merge pull request #935 from python-discord/bug/mod/932/modlog-ignore-dmsGravatar Joseph Banks2020-06-10-0/+4
| |\ \ \ | | | | | | | | | | ModLog: ignore DMs in the message delete listener
| | * \ \ Merge branch 'master' into bug/mod/932/modlog-ignore-dmsGravatar Joseph Banks2020-06-10-1061/+2576
| | |\ \ \ | | |/ / / | |/| | |
| * | | | Add Python Atlanta to guild whitelistsGravatar Joseph Banks2020-06-09-0/+1
| | | | |
| | * | | 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
* | | | | Incidents: add #incidents-archive webhook constantGravatar kwzrd2020-06-11-1/+2
| | | | |
* | | | | Incidents: add #incidents-archive channel constantGravatar kwzrd2020-06-11-0/+2
| | | | |
* | | | | Incidents: create Signal enum & link members with emojisGravatar kwzrd2020-06-08-0/+10
| | | | |
* | | | | Incidents: add new emoji constantsGravatar kwzrd2020-06-08-0/+8
| | | | |
* | | | | Incidents: add incidents module & new ext boilerplateGravatar kwzrd2020-06-08-1/+17
|/ / / /
* | | | Merge pull request #983 from python-discord/bug/backend/stats-category-checkGravatar Dennis Pham2020-06-07-1/+2
|\ \ \ \ | | | | | | | | | | Fix AttributeError for category check
| * \ \ \ Merge branch 'master' into bug/backend/stats-category-checkGravatar Dennis Pham2020-06-07-33/+96
| |\ \ \ \ | |/ / / / |/| | | |
* | | | | 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 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.
| * | | | | Fix a bad check in get_staff_channel_count.Gravatar Leon Sandøy2020-05-31-7/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This also changes a few aesthetic problems pointed out in review by @MarkKoz and @kwzrd.
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-09 09:05:52 +0000