bot - A mirrored copy of the python-discord/bot repository.

	Commit message (Collapse)	Author	Age	Lines
*	PR #1151 Sync: remove confirmation	kwzrd	2020-09-26	-519/+24
\|\
\| *	Sync: update sync() docstring	MarkKoz	2020-09-26	-3/+1
\| \|
\| *	Sync: remove _asdict comment	MarkKoz	2020-09-23	-1/+1
\| \| \| \| \| \| \| \|	The comment doesn't contribute anything.
\| *	Merge branch 'master' into feat/backend/1075/remove-syncer-confirm	MarkKoz	2020-09-22	-2227/+2207
\| \|\
\| * \|	Sync: refactor conditional for sending message	Mark	2020-09-22	-1/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The ternary is a bit confusing. Co-authored-by: Numerlor <[email protected]>
\| * \|	Fix test for sync message being edited	MarkKoz	2020-09-07	-1/+3
\| \| \|
\| * \|	Sync: remove confirmation	MarkKoz	2020-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
* \| \|	Merge pull request #1161 from bast0006/feature-bast-user-token-notify	Mark	2020-09-25	-39/+188
\|\ \ \ \| \| \| \| \| \| \| \|	Add userid decoding and user token detection to the token removal moderation feature
\| * \| \|	Remove redundant is_valid_userid function	Bast	2020-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 detection	Bast	2020-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 ↵	Bast	2020-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 changes	Bast	2020-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-notify	Bast	2020-09-21	-270/+686
\| \|\ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Resynchronize changes with the new cog folder arrangement
\| * \| \| \|	Make token_remover check basic HMAC validity (not low entropy)	Bast	2020-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 ↵	Bast	2020-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-levels	Mark	2020-09-23	-2/+2
\|\ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \|	Adjust verification & incidents log levels
\| * \| \| \| \|	Incidents: bump archive log to INFO level	kwzrd	2020-09-23	-1/+1
\| \| \| \| \| \|
\| * \| \| \| \|	Verification: reduce request dispatch log level	kwzrd	2020-09-23	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Avoid information duplication in production logs.
* \| \| \| \| \|	Fix use of expanded infraction response for username	MarkKoz	2020-09-23	-1/+1
\|/ / / / / \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Fixes BOT-9A
* \| \| \| \|	Update format_user to remove username and add ID	Joe Banks	2020-09-23	-4/+2
\| \| \| \| \|
* \| \| \| \|	Clean: fix mention in mod log message	MarkKoz	2020-09-22	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Fixes BOT-99
* \| \| \| \|	Avoid using discord.Object's repr as the username for infraction search	MarkKoz	2020-09-22	-0/+7
\| \| \| \| \|
* \| \| \| \|	Fix AttributeError for infraction user searches via the group	MarkKoz	2020-09-22	-1/+1
\| \| \| \| \|
* \| \| \| \|	Fix future date check in snowflake converter	MarkKoz	2020-09-22	-1/+1
\| \| \| \| \|
* \| \| \| \|	Merge pull request #1126 from ↵	Mark	2020-09-22	-37/+22
\|\ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	python-discord/feat/info/1125/user-cmd-whitelist-modmail Whitelist the modmail category for displaying verbose infraction info from the user command
\| * \ \ \ \	Merge branch 'master' into feat/info/1125/user-cmd-whitelist-modmail	MarkKoz	2020-09-22	-3054/+2635
\| \|\ \ \ \ \ \| \|/ / / / / \|/\| \| \| \| \|
* \| \| \| \| \|	Merge pull request #1061 from python-discord/feat/frontend/533/mod-log-names	Mark	2020-09-22	-207/+209
\|\ \ \ \ \ \ \| \|_\|_\|_\|_\|/ \|/\| \| \| \| \|	Use mentions for users in mod logs and infraction search results
\| * \| \| \| \|	Filtering: add missing space to log msg	Mark	2020-09-22	-1/+1
\| \| \| \| \| \|
\| * \| \| \| \|	Fix type annotation for expanded infractions	MarkKoz	2020-09-22	-2/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The `_utils.Infraction` alias does not cover nested data structures. Therefore, it's inappropriate for expanded infraction API responses.
\| * \| \| \| \|	Merge branch 'master' into feat/frontend/533/mod-log-names	MarkKoz	2020-09-22	-3016/+2690
\| \|\ \ \ \ \ \| \|/ / / / / \|/\| \| \| \| \|
* \| \| \| \| \|	Merge pull request #1168 from python-discord/feat/latency	Senjan21	2020-09-22	-1/+69
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Latency cog for checking ping.
\| * \ \ \ \ \	Merge branch 'master' into feat/latency	Xithrius	2020-09-22	-1463/+224
\| \|\ \ \ \ \ \ \| \|/ / / / / / \|/\| \| \| \| \| \|
* \| \| \| \| \| \|	Merge pull request #1163 from ↵	Sebastiaan Zeeff	2020-09-22	-843/+168
\|\ \ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	python-discord/sebastiaan/features/use-async-rediscache-package Use `async-rediscache` package for our redis caches
\| * \ \ \ \ \ \	Merge branch 'master' into sebastiaan/features/use-async-rediscache-package	Sebastiaan Zeeff	2020-09-22	-1136/+1003
\| \|\ \ \ \ \ \ \ \| \|/ / / / / / / \|/\| \| \| \| \| \| \|
* \| \| \| \| \| \| \|	Merge pull request #1164 from python-discord/sebastiaan/bugs/duckpond	Dennis Pham	2020-09-21	-630/+102
\|\ \ \ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Several improvements to duckpond
\| * \| \| \| \| \| \| \|	Use `has_any_role` decorator instead of old `with_role` decorator	Den4200	2020-09-21	-2/+2
\| \| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \| \|	Merge branch 'master' into sebastiaan/bugs/duckpond	Den4200	2020-09-21	-506/+901
\| \|\ \ \ \ \ \ \ \ \| \|/ / / / / / / / \|/\| \| \| \| \| \| \| \|
* \| \| \| \| \| \| \| \|	Merge branch 'bug/1142/fix-everyone-ping' into master	Daniel Brown	2020-09-21	-62/+47
\|\ \ \ \ \ \ \ \ \
\| * \ \ \ \ \ \ \ \	Merge branch 'master' into bug/1142/fix-everyone-ping	Kieran Siek	2020-09-19	-88/+808
\| \|\ \ \ \ \ \ \ \ \ \| \| \| \|_\|_\|_\|_\|/ / / \| \| \|/\| \| \| \| \| \| \|
\| * \| \| \| \| \| \| \| \|	Add everyone_ping filter.	kosayoda	2020-09-08	-11/+47
\| \| \| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \| \| \|	Remove everyone_ping rule from antispam.	kosayoda	2020-09-07	-152/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The feature will be moved to the filtering cog.
\| * \| \| \| \| \| \| \| \|	Add test for everyone_ping rule.	kosayoda	2020-09-05	-0/+102
\| \| \| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \| \| \|	Detect pings after removing codeblocks.	kosayoda	2020-09-05	-6/+9
\| \| \| \| \| \| \| \| \| \|
\| \| \| * \| \| \| \| \| \|	Lower duckpond threshold to increase activity	Sebastiaan Zeeff	2020-09-20	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	There's not a lot of activity in our duckpond at the moment. To activate our duckies, I've decreased the duckpond threshold to 4. This means that a message will now be relayed once it's been ducked four times. Let's get all of our ducks in a row. Signed-off-by: Sebastiaan Zeeff <[email protected]>
\| \| \| * \| \| \| \| \| \|	Add command to relay a message to duckpond	Sebastiaan Zeeff	2020-09-20	-1/+11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This commit adds a command that allows admins to manually relay a message to the duckpond, regardless of duck counts and the checks done in the reaction event handler. Signed-off-by: Sebastiaan Zeeff <[email protected]>
\| \| \| * \| \| \| \| \| \|	Use helper for duckpond's locked relay feature	Sebastiaan Zeeff	2020-09-20	-15/+20
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I've created a helper for duckpond's relay feature to allow me to use it separately from the command we're planning to add to the Cog. I opted not to include the lock in the original relay method to separate the logic more clearly. Signed-off-by: Sebastiaan Zeeff <[email protected]>
\| \| \| * \| \| \| \| \| \|	Remove unit tests for duck pond	Sebastiaan Zeeff	2020-09-20	-548/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I've removed the unit tests for duckpond in concordance with the new policy for writing unit tests for the bot The tests were unnecessarily complicated, difficult to maintain, and slowed development. Signed-off-by: Sebastiaan Zeeff <[email protected]>
\| \| \| * \| \| \| \| \| \|	Fix relay race condition in duckpond using a lock	Sebastiaan Zeeff	2020-09-20	-7/+17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Our duckpond suffered from a race condition: If multiple raw reaction events were received in quick succession and a message had enough ducks to take it over the duckpond threshold, the message would be relayed multiple times. The reason this happened is because the green checkmark emoji that stops a message from being relayed multiple times is only added after the message has been relayed. This means that multiple event triggers can make it past the green checkmark check before any of them has a chance to add a green checkmark. The solution was to create a relay lock that needs to be acquired before checking for the presence of a green checkmark and is only released after adding a green checkmark. This prevents multiple events from making it past the sentinel check. As our Cogs are potentially initialized before the event loop is created, the lock is load lazily when needed. Signed-off-by: Sebastiaan Zeeff <[email protected]>
\| \| \| * \| \| \| \| \| \|	Add channel blacklist for duckpond	Sebastiaan Zeeff	2020-09-20	-4/+38
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	As announcements already get a lot of exposure and have a high risk of getting "ducked", duckpond will now ignore those channels and never relay those announcements to our duckpond. Signed-off-by: Sebastiaan Zeeff <[email protected]>
\| \| \| * \| \| \| \| \| \|	Ignore non-staff messages for our duckpond	Sebastiaan Zeeff	2020-09-20	-1/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Some of our members have expressed concern that their messages would be "ducked" by staff members and relayed to the staff-only duckpond. Since duckpond is supposed to be a funny, staff-only affair, I've made duckpond ignore messages from non-staff members. Signed-off-by: Sebastiaan Zeeff <[email protected]>