| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The function `_delete_reminder` was called twice, once in
`schedule_reminder`, which calls `send_reminder`, then another in
`send_reminder` itself. This led to a 404 response from the site api, as
the reminder was already deleted the first time.
Fixes BOT-6W
|
| |\
| |
| | |
Relay all DMs sent to the bot to #dm_log
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Allow ordering talentpool/bigbrother watched users by oldest added
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
python-discord/bug/info/1050/remove-help-reactions-404
Suppress NotFound when removing help command reactions
|
| | |\ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Users can no longer see available channels if they're on cooldown. They
will instead see a special "cooldown" channel which will explain
what's going on.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
The message may be deleted somehow before the wait_for times out.
Fixes #1050
Fixes BOT-6X
|
| | | | |
|
| | |\ \
| |/ /
|/| | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |\
| |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
Sanitize bot output
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | | |
Co-authored-by: Leon Sandøy <[email protected]>
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
The kwarg `active=False` is already being passed in `apply_kick`,
therefore passing it in the parent callers result in a TypeError.
Fixes #976
Fixes BOT-5P
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The following communities are whitelisted by this commit:
- Django
- Programming Discussions
- JetBrains Community
- Raspberry Pi
- Programmers Hangout
- SpeakJS
- DevCord
- Unity
- Programmer Humor
- Microsoft Community
Most of these are partners, or otherwise friendly communities that aren't worth pinging mods over.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If you're typing up a reply and the bot gets another DM while you're
typing, you might accidentally send your reply to the wrong person.
This could happen even if you're very attentive, because it might be a
matter of milliseconds. The complexity to prevent this isn't worth the
convenience of the feature, and it's nice to get rid of the caching as
well, so I've decided to just make .reply require a user for every
reply.
https://github.com/python-discord/bot/issues/1041
|
| | | |\
| |_|/
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
python-discord/1038_allow_role_mentions_in_specific_areas
Allow role mentions in specific areas
|
| | |\ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It was attempting to schedule a dictionary instead of a coroutine.
Fixes #1043
Fixes BOT-6Y
|
| |\ \ \ \
| | | | |
| | | | | |
Scheduler Redesign
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It'd fail to schedule the coroutine otherwise anyway. There is also the
potential to close the coroutine, which may be unexpected to see for a
coroutine that was already running (despite being documented).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Showing the task ID in the logs makes them distinguishable from logs for
other tasks.
The coroutine state is logged because it may come in handy while
debugging; the coroutine inspection check hasn't been proven yet in
production.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The coroutine may cancel the scheduled task, which would also trigger
the finally block. The coroutine isn't necessarily finished when it
cancels the task, so it shouldn't be closed in this case.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The task is already popped from the dict, so there is no need to delete
it afterwards.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This prevents unawaited coroutine warnings.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|