| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Without this, it is difficult to know precisely who the user that is
DMing us is, which might be useful to us.
https://github.com/python-discord/bot/issues/1041
|
| | | | |/ / /
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 042f472a
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | |\ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Also now catches the exception if a user has disabled DMs, and adds a
red cross reaction.
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This shouldn't be used as a replacement for ModMail, but I think it
makes sense to have the feature just in case #dm-log provides an
interesting use-case where responding as the bot makes sense.
It's a bit of a curiosity, and Ves hates it, but I included it anyway.
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Some of the tests were failing because they were expecting send_webhook
to be a method of the DuckPond cog, other tests simply were no longer
applicable, and have been removed.
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | | |
| | | | | | |
| | | | | | | |
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |_|_|_|/ /
|/| | | | |
| | | | | | |
Adjust description and include link to docs
|
| | |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Naming it "task" is inaccurate because `create_task` accepts a coroutine
rather than a Task. What it does is wrap the coroutine in a Task.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
It's redundant. After all, this scheduler cannot schedule anything else.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The ability to use the `in` operator makes this obsolete. Callers can
check themselves if a task exists before they try to cancel it.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Makes them easier to identify when debugging.
|