| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
| |
* Remove obsolete log message
* Shorten a log message which was the only line in the entire module
over 100 characters
|
| |
|
|
|
|
|
|
|
|
|
| |
A user may leave the guild before their role can be changed. Sometimes,
there could also be role hierarchy issues or other network issues. It's
not productive to halt everything and just dump these as exceptions to
the loggers. The error handler provides a more graceful approach to
these exceptions.
* Add a wrapper function around `add_roles` & `remove_roles` which
catches exceptions
|
| |
|
|
|
|
|
| |
Resetting permissions relied on getting the member from the cache, but
the member was already removed from the cache prior to resetting the
role. Now the member is passed directly rather than relying on the
cache.
|
| |
|
|
| |
Users should know they can close their own channels.
|
| | |
|
| |
|
|
|
|
|
| |
Overwrites had issues syncing with channels in the category.
* Remove update_category_permissions; obsolete
* Add constant for the cooldown role wrapped in a discord.Object
|
| |
|
|
|
| |
Claimants will have a special role that needs to be removed rather than
using member overwrites for the category.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
python-discord/bug/frontend/870/help-channel-dm-category
HelpChannels: fix AttributeError getting a category for a DMChannel
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Fix wrong exception type in syncing
|
| | |\ \
| |/ /
|/| | |
|
| | | |
| | |
| | | |
We want our members to use the paste site to share text-based files instead of them sharing the files as attachments on Discord. As `.md`, a file extensions used for plain-text files with markdown formatting, is such a text file, I've removed it from the anti-malware whitelist.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
python-discord/help-channels-keep-dormant-invocation
Reverse deletion of `!dormant` invocation messages
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
PR #868 introduced the automatic deletion of the message that issued the `!dormant` command. The idea behind this was that moving the channel to the dormant category makes it obvious that a channel has gone dormant and the message would only serve as visual clutter.
However, removing the command invocation also means that it's less obvious why a channel was moved to the dormant category. As the message gets deleted almost immediately, you have to be actively watching the channel to know that the command was issued and who issued it. This has already caused some confusion where helping members where left wondering why a channel suddenly went dormant while they felt that the conversation was still ongoing.
To improve the user experience, this commit removes the deletions of the command invocation messages.
|
| | | |
| | |
| | |
| | | |
resolved tag name
|
| | | |
| | |
| | |
| | | |
staff
|
| |\ \ \
| | | |
| | | |
| | | | |
After resolving the merge conflicts created by the recent stats addition, I'm merging this into master. No functional changes were made during conflict resolution (hopefully) and the merge has been tested.
|
| |/| | |
| | | |
| | | |
| | | | |
Numerlor-help-dormant-feedback
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`ctx.author` that is used to populate the dict returns
a `Member` object in most cases while only `User` was documented
as a possible value.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the new addition of non latin-11 chars in channel names - which get logged,
the logging to files fails on those entries on OSs where the default
encoding is not utf8 or an other encoding capable of handling them.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Deleting the channel from the claimant cache on
invokation of the dormant command prevents users running
the command multiple times before the bot moves it.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Reversing the order ensures the task is not cancelled
when moving to dormant fails which gives a fallback to move it
after the initial period of time.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In a testing environment, the bot may try to edit the message of a
different bot. Therefore, the author of the message should be checked
to ensure the current bot sent it.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: MarkKoz <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: MarkKoz <[email protected]>
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Only resetting the permission caused the overwrites for the users
to remain on the category, potentially piling up and causing further issues.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Pairing users to channels was a design flaw,
because the keys didn't get overwritten.
This allowed multiple users to access the dormant command
for the running session of the bot.
Replacing this with a reversed paring fixes both issues
because the cache is overwritten on channel activation.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
After the dormant command is used and the permissions
are restored for the user that started the session,
the task for restoring them after the claim time
has passed is no longer necessary.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Removing the `with_role` check from the command and
replcaing it with a new `dormant_check` that's used in the body,
which also checks against a cache of users that started the sessions,
allows them to close their own channels along with the role check.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
StatsD integration
|
| | | | | | |
|
| | | | | | |
|
| | |\ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Mark <[email protected]>
|
MarkKoz
Shirayuki Nekomata
kwzrd
Sebastiaan Zeeff
Joseph Banks
Numerlor