|  | Commit message (Collapse) | Author | Age | Lines | 
|---|
| ... |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Replace the `_get_arg_value` call with `function.get_arg_value` cause
the latter makes use of bound arguments, which are more accurate. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | This fixes race conditions between editing, deleting, and sending a
reminder. If one operation is already happening, the others will be
aborted. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | This is a more advanced version meant to eventually replace the
`_get_arg_values` in decorators.py. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Bound arguments are more convenient to work with than the raw args
and kwargs. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Supporting ID retrieval by arg name or position made for a confusing
interface. I also doubt it would have been used much. A callable can
achieve the same thing, albeit with a little more code.
Now the decorator instead supports passing an ID directly or a callable. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | This will be used to prevent race conditions on a resource by stopping
all other access to the resource once its been acquired. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | It's fine to accept an int since it'll get converted to a string anyway. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Only one call was benefiting from that function also cancelling the
task. Therefore, the function was redundant and has been replaced with
a direct request to delete.
This change has the consequence of also fixing reminder tasks cancelling
themselves. That issue was potentially suppressing errors (such as the
duplicate DELETE request which was fixed earlier). Under normal
circumstances, the scheduler will automatically removed finished tasks
so tasks won't need to cancel/remove themselves. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | `send_reminder` already deletes the reminder so it's redundant to
delete it in the scheduled task too. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| |\| | | | | |  | 
| | |\ \ \ \ \  
| | | | | | | 
| | | | | | | | Add userid decoding and user token detection to the token removal moderation feature | 
| | | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | | extract_user_id(id) is not None does the same job and is not worth the extra function | 
| | | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | | Clean up mock usage, docstrings, unnecessarily split-lined function calls | 
| | | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | | the current server
Also adjust the naming and purposes of the format messages to KNOWN and UNKNOWN token messages. | 
| | | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | 
| | | | | | | | 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 | 
| | | |\ \ \ \ \  
| | | | | | | | 
| | | | | | | | 
| | | | | | | | | Resynchronize changes with the new cog folder arrangement | 
| | | | | | | | | 
| | | | | | | | 
| | | | | | | | 
| | | | | | | | | Handles cases like xxx.xxxxx.xxxxxxxx where a user has intentionally censored part of a token, and will not consider them "valid" | 
| | | | | | | | | 
| | | | | | | | 
| | | | | | | | 
| | | | | | | | 
| | | | | | | | 
| | | | | | | | 
| | | | | | | | | 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 | 
| | |\ \ \ \ \ \ \  
| | | | | | | | | 
| | | | | | | | | | Adjust verification & incidents log levels | 
| | | | | | | | | | |  | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | Avoid information duplication in production logs. | 
| | |/ / / / / / /  
| | | | | | | |   
| | | | | | | |   
| | | | | | | | | Fixes BOT-9A | 
| | | | | | | | | |  | 
| | | | | | | | | 
| | | | | | | | 
| | | | | | | | 
| | | | | | | | | Fixes BOT-99 | 
| | | | | | | | | |  | 
| | | | | | | | | |  | 
| | | | | | | | | |  | 
| | |\ \ \ \ \ \ \  
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | python-discord/feat/info/1125/user-cmd-whitelist-modmail
Whitelist the modmail category for displaying verbose infraction info from the user command | 
| | | |\ \ \ \ \ \ \  
| | |/ / / / / / /  
| |/| | | | | | | |  | 
| | |\ \ \ \ \ \ \ \  
| | |_|_|_|_|/ / /  
| |/| | | | | | | | Use mentions for users in mod logs and infraction search results | 
| | | | | | | | | | |  | 
| | | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | 
| | | | | | | | | | The `_utils.Infraction` alias does not cover nested data structures.
Therefore, it's inappropriate for expanded infraction API responses. | 
| | | |\ \ \ \ \ \ \  
| | |/ / / / / / /  
| |/| | | | | | | |  | 
| | |\ \ \ \ \ \ \ \  
| | | | | | | | | | 
| | | | | | | | | | | Latency cog for checking ping. |