|  | Commit message (Collapse) | Author | Age | Lines | 
|---|
| ... |  | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Booleans are less error-prone than strings. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Ensure the cancellation will be under the lock once the lock is added. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Referencing internal functions in public-facing documentation is not
helpful to users. | 
| | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | If the lock causes the function to abort, a new channel shouldn't be
made available. However, the only way to know it's aborted from the
outside would be through a return value or global variable. Neither seem
as nice as just just using `create_task` within the lock to avoid
having `move_to_available` hold the lock. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Normally exceptions are only logged when tasks are garbage collected.
This wrapper will allow them to be logged immediately through a done
callback. This is similar to how the Scheduler logs errors. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | The race condition is when a user claims a channel while their other
channel is being unclaimed. Specifically, it's while their cooldown is
being removed.
The lock ensures that either the cooldown will be re-applied after it's
removed or that it won't be removed since `unclaim_channel` will see the
user has another claimed channel. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | It's been determined that asyncio.Lock is safe to use in such manner.
Therefore, replace LockGuard entirely with asyncio.Lock. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Narrow the scope of `move_to_dormant` to just moving the channel.
Following the design of `claim_channel`, make `unclaim_channel` handle
cooldowns and unpinning. | 
| | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Move significant code related to stats to a separate module. | 
| | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | It's conceivable for a user to be able to quickly send a message in all
available channels before the code has a chance to add the cooldown
role.
Place a lock on the author to prevent the claim code from running
multiple times for the same user. | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | It feels safer to do this since the init task moves channels to
different categories and the listeners check if channels are in certain
categories. | 
| | |_|_|_|_|_|_|_|_|_|_|/ / / /  
|/| | | | | | | | | | | | | |   
| | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | | | Use the `lock_arg` decorator to keep a separate lock for each channel
rather than a single lock used by all messages. Separate the core logic
in `on_message` into a separate function to facilitate the use of
`lock_arg` - not everything in `on_message` needs to be under the lock. | 
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Add check does user have permission to get raw message and re-enable raw command | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |/ / / / / / / / / / / / / / /  
|/| | | | | | | | | | | | | | | |  | 
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | | Make nomination reason optional. | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |/ / / / / / / / / / / / / / / /  
|/| | | | | | | | | | | | | | | | |  | 
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |_|_|_|_|_|_|/ / / / / / / / / /  
|/| | | | | | | | | | | | | | | | |  | 
| |/ / / / / / / / / / / / / / / /  
| | | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | | | | Related to #1342. | 
| | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Co-authored-by: Dennis Pham <[email protected]> | 
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | Co-authored-by: Dennis Pham <[email protected]> | 
| | | | | | | | | | | | | | | | | |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |/ / / / / / / / / / / / / / /  
|/| | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | | | | The cogs folder no longer exists, but the merge command was able to automagically find the correct files to merge into. Nomination reason is now optional. | 
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | | Fix flake8 pre-commit hook running through PyCharm | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |/ / / / / / / / / / / / / / / /  
|/| | | | | | | | | | | | | | | | |  | 
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| | | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | | | `!user` command says if a user is "Verified", rather than "Pending" | 
| | | | | | | | | | | | | | | | | | | |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |/ / / / / / / / / / / / / / / / /  
|/| | | | | | | | | | | | | | | | |   
| | | | | | | | | | | | | | | | | | | swfarnsworth/info | 
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| | | | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | | | | | | Some bug fixes | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| |/ / / / / / / / / / / / / / / / / /  
|/| | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \  
| | | |_|_|_|_|_|_|_|_|/ / / / / / / /  
| | |/| | | | | | | | | | | | | | | | |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |  | 
| | | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | | |  | 
| | | | | | | | | | | | | | | | | | | | | | |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |  | 
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |  | 
| | | | | | | | | | | | | | | | | | | | | | | | |  |