aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Changed dm_relay to include user id in webhook when sending attachments.Gravatar wookie1842020-10-02-1/+5
|
* Add use_cached argument to send_attachments, and change it to default to FalseGravatar wookie1842020-10-02-1/+2
|
* Changed send_attachments so kwargs could be given and would be passed to send()Gravatar wookie1842020-10-02-14/+13
|
* Merge pull request #860 from ks129/discord-py-upgrade-migrateGravatar Joe Banks2020-10-02-122/+77
|\ | | | | discord.py 1.3.x Functionality Migrating
| * Merge branch 'master' into discord-py-upgrade-migrateGravatar MarkKoz2020-10-02-5710/+11177
| |\ | |/ |/|
* | Merge pull request #1205 from soumitradev/source_escape_markdownGravatar Matteo Bertucci2020-10-02-2/+4
|\ \ | | | | | | Escape markdown in faulty source commands
| * \ Merge branch 'master' into source_escape_markdownGravatar Soumitra Shewale2020-10-02-2/+2
| |\ \ | |/ / |/| |
* | | PR #1206 PEPs: move URL link to titleGravatar kwzrd2020-10-02-2/+2
|\ \ \
| * | | Update !pep 0 commandGravatar Soumitra Shewale2020-10-02-1/+1
| | | |
| * | | Move PEP command embed URL to titleGravatar Soumitra Shewale2020-10-02-1/+1
|/ / / | | | | | | | | | Closes #1176
| * | Get rid of codeblock in souce commitGravatar Soumitra Shewale2020-10-02-2/+3
| | | | | | | | | | | | | | | | | | Double backtick will break if argument contains a double backtick, so getting rid of the codeblock itself makes more sense in my opionion. Also fix the style issue with multiline string by storing the escaped arg in another variable
| * | LinterGravatar Soumitra Shewale2020-10-02-1/+2
| | | | | | | | | | | | I had flake8 turned off in my dpy env -_-
| * | Escape markdown in faulty source commandsGravatar Soumitra Shewale2020-10-02-2/+2
|/ / | | | | | | Closes #1177
* | PR #1198: Remove alias cogGravatar kwzrd2020-10-01-102/+3
|\ \
| * | Remove special handling for the alias cog in the !source commandGravatar MarkKoz2020-10-01-15/+3
| | | | | | | | | | | | It's obsolete code because the cog has been removed.
| * | Remove alias cogGravatar MarkKoz2020-09-30-87/+0
| | | | | | | | | | | | | | | | | | | | | | | | Last few aliases are an anomaly since #1124 was merged. The remaining aliases are seldom used. The code isn't exactly clean and it has some maintenance costs. Resolves #1159
* | | Merge pull request #1201 from python-discord/bug/fun/1183/pond-ignore-dmGravatar Mark2020-10-01-0/+13
|\ \ \ | | | | | | | | Duck pond: ignore reactions in DMs
| * | | Duck pond: ignore reaction events from other guildsGravatar MarkKoz2020-10-01-2/+8
| | | |
| * | | Duck pond: ignore reactions in DMsGravatar MarkKoz2020-09-30-0/+7
| |/ / | | | | | | | | | | | | | | | | | | | | | Also handle the channel not being found, which may be due to a cache issue or because it got deleted. Fixes #1183 Fixes BOT-8T
* | | Merge pull request #1199 from ↵Gravatar Matteo Bertucci2020-10-01-1/+5
|\ \ \ | | | | | | | | | | | | | | | | python-discord/bug/backend/1181/wait-for-deletion-404 Catch 404 in wait_for_deletion when reacting
| * \ \ Merge branch 'master' into bug/backend/1181/wait-for-deletion-404Gravatar Matteo Bertucci2020-10-01-1/+1
| |\ \ \ | |/ / / |/| | |
* | | | Merge pull request #1200 from python-discord/bug/mod/1182/deleted-msg-null-charGravatar Matteo Bertucci2020-10-01-1/+1
|\ \ \ \ | |_|/ / |/| | | Remove null chars before posting deleted messages
| * | | Remove null chars before posting deleted messagesGravatar MarkKoz2020-09-30-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | Our API doesn't allow null characters in the content field. It may be present because of a self bot that is able to send such character. Fixes #1182 Fixes BOT-8E
| * / Catch 404 in wait_for_deletion when reactingGravatar MarkKoz2020-09-30-1/+5
|/ / | | | | | | | | | | The message may be deleted before the bot gets a chance to react. Fixes #1181
* | PR #1191 Verification: broaden 50_007 error handlingGravatar kwzrd2020-09-29-11/+30
|\ \
| * | Incidents: reduce timeout log to info levelGravatar kwzrd2020-09-27-1/+1
| | | | | | | | | | | | | | | | | | This shouldn't be a warning, as we cannot do anything about it. Fixes BOT-8X
| * | Verification: apply 'safe_dm' to all DM dispatchesGravatar kwzrd2020-09-27-5/+7
| | | | | | | | | | | | | | | | | | Now, when we send a DM and it fails: * Ignore if due to disabled DMs * Log exception otherwise
| * | Verification: move disabled DM handling into helperGravatar kwzrd2020-09-27-5/+22
| | | | | | | | | | | | | | | | | | Note that we were previously only catching 403. As the docstring explains, we will now catch any Discord exception and only look at the the code, rather than the status.
* | | Merge remote-tracking branch 'origin/master' into masterGravatar Matteo Bertucci2020-09-27-585/+101
|\| |
| * | Relock Pipfile to update async-redis.Gravatar Leon Sandøy2020-09-27-62/+70
| | | | | | | | | | | | | | | | | | This also bumps minor versions of several other packages. I've spun up the bot and played around with it, and run all unit tests. Everything still seems to be in order.
| * | Add the video to the welcome DM.Gravatar Leon Sandøy2020-09-27-4/+7
| | | | | | | | | | | | | | | This rewords the welcome DM, and adds the new Welcome To Python Discord video to it.
| * | PR #1151 Sync: remove confirmationGravatar kwzrd2020-09-26-519/+24
| |\ \
| | * | Sync: update sync() docstringGravatar MarkKoz2020-09-26-3/+1
| | | |
| | * | Sync: remove _asdict commentGravatar MarkKoz2020-09-23-1/+1
| | | | | | | | | | | | | | | | The comment doesn't contribute anything.
| | * | Merge branch 'master' into feat/backend/1075/remove-syncer-confirmGravatar MarkKoz2020-09-22-2227/+2207
| | |\ \
| | * | | Sync: refactor conditional for sending message Gravatar Mark2020-09-22-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | The ternary is a bit confusing. Co-authored-by: Numerlor <[email protected]>
| | * | | Fix test for sync message being editedGravatar MarkKoz2020-09-07-1/+3
| | | | |
| | * | | Sync: remove confirmationGravatar MarkKoz2020-09-07-518/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The confirmation was intended to be a safe guard against cache issues that would cause a huge number of roles/users to deleted after syncing. With `wait_until_guild_available`, such cache issue shouldn't arise. Therefore, this feature is obsolete. Resolve #1075
* | | | | Allow !role for any staff roleGravatar Matteo Bertucci2020-09-27-2/+2
| | | | | | | | | | | | | | | | | | | | Closes #1173
* | | | | Allow !eval in #code-help-voiceGravatar Matteo Bertucci2020-09-27-1/+3
|/ / / /
* | | | Merge pull request #1161 from bast0006/feature-bast-user-token-notifyGravatar Mark2020-09-25-39/+188
|\ \ \ \ | | | | | | | | | | Add userid decoding and user token detection to the token removal moderation feature
| * | | | Remove redundant is_valid_userid functionGravatar Bast2020-09-25-33/+27
| | | | | | | | | | | | | | | | | | | | extract_user_id(id) is not None does the same job and is not worth the extra function
| * | | | Change the mod alert message component for the user token detectionGravatar Bast2020-09-24-46/+23
| | | | | | | | | | | | | | | | | | | | Clean up mock usage, docstrings, unnecessarily split-lined function calls
| * | | | Add BOT vs USER token detection, properly handling bot tokens for bots in ↵Gravatar Bast2020-09-24-13/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the current server Also adjust the naming and purposes of the format messages to KNOWN and UNKNOWN token messages.
| * | | | Implement review-suggested changesGravatar Bast2020-09-24-67/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | userid -> user ID maybevalid -> maybe_valid remove collections import and added a new function that handles the "format user ID log message" and should_ping_everyone feature
| * | | | Merge branch 'master' into feature-bast-user-token-notifyGravatar Bast2020-09-21-270/+686
| |\ \ \ \ | | | | | | | | | | | | | | | | | | Resynchronize changes with the new cog folder arrangement
| * | | | | Make token_remover check basic HMAC validity (not low entropy)Gravatar Bast2020-09-19-6/+55
| | | | | | | | | | | | | | | | | | | | | | | | Handles cases like xxx.xxxxx.xxxxxxxx where a user has intentionally censored part of a token, and will not consider them "valid"
| * | | | | Add feature to token_remover: log detected user ID, and ping if it's a user ↵Gravatar Bast2020-09-19-19/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in the server Updated tests This comes with a change that a user ID must actually be able to be decoded into an integer to be considered a valid token
* | | | | | Merge pull request #1171 from python-discord/kwzrd/log-levelsGravatar Mark2020-09-23-2/+2
|\ \ \ \ \ \ | | | | | | | | | | | | | | Adjust verification & incidents log levels
| * | | | | | Incidents: bump archive log to INFO levelGravatar kwzrd2020-09-23-1/+1
| | | | | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-25 21:23:20 +0000