| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | |\ \
| | | |
| | | | |
include Thread & PrivateChannel in get_or_fetch_channel return types
|
| | | |\ \
| | |/ /
| |/| | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Made the tag more brief without any substantial changes to its overall approach.
Co-authored-by: wookie184 <[email protected]>
|
| | |/ / |
|
| | | |
| | |
| | |
| | | |
The nomination cache was recently removed, so accessing that no longer works.
|
| | |/ |
|
| | |\
| | |
| | | |
Don't close already closed posts
|
| | |/ |
|
| | |\
| | |
| | | |
Link directly to the sqlite3 placeholder howto
|
| | | |\
| | |/
| |/| |
|
| | |\ \
| | | |
| | | | |
Help forum improvements
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
thread_create events are triggered before the thread's starter message is available, so listening for starter messages with on_message instead ensures we have a message object to use.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I decided to keep the archive logic simple, and just go for 30 minutes since last message, rather than the hybrid of 30 mins + 10 depending on who sent the last message.
The reason for using the hybrid approach previously was due to us running out of channels frequently
Since this is no longer a problem, I decided to keep the logic simple.
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| | |\ \
| | | |
| | | | |
Bump bot core version
|
| | | | |
| | | |
| | | |
| | | | |
These errors can be caused by the message being deleted, or the message being in an archived thread
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| | |\ \
| | | |
| | | | |
Misc Fixes For Help Forum
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Co-authored-by: Boris Muratov <[email protected]>
Co-authored-by: Amrou Bellalouna <[email protected]>
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In the case of an image or other media as the starter message, the
formatted message in the help DM will be empty, which is invalid for the
embed. We populate the field with some more useful text in this case.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Similar to 555ed4e9, the pagination utility needs to catch when it's
trying to act on an archived thread.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The wait_for_deletion utility would try to remove reactions from a
message after the timeout expires, which would normally be fine. In
threads however, they can be closed while waiting for the timeout to
expire. In such a case, the bot will try to remove the reactions after
the channel has been closed and fail. A special exception was added for
this case to do nothing, since this is only a QoL feature.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The old method for detecting deleted opener messages does not seem to
work, probably because the message is fetched from a cache or similar.
Instead we simply try/except pinning the message and pass if the pinning
failed.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We try to remove the cooldown role from users before checking if the
user is still in the server, which can cause an error since the thread
object will just contain `None` as the user.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When discord sends us the thread create event in help channels, it is
not ready to perform other operations on the thread such as getting or
pinning messages. This causes it to error out when we try to do these
actions and claim that those channels don't exist. Instead, we sleep for
a short time to try and wait for it to be ready.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The current warning log includes the thread name, which means the log
message varies wildly between threads. This causes issues with sentry
since the actual error message gets trimmed, and sentry fails to group
issues from this log as they appear as different messages.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | |\ \
| | | |
| | | | |
Send DM message to help post opener sooner in the process
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
This is to give Discord time to make the thread actually avaiulable to be posted in for the send_opened_post_message call
Closes #2334 Closes BOT-3AW
|
| | |\ \
| | | |
| | | | |
Update help channel system to use forum channels
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
It is expected that this code will be delete whent he new fitler cog is added, and we start filtering on thread names genericly.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This was due to the hlep channels causing many events top be pushed to modlog due to how the old system worked. Now that we use a forum chanel, this is no longer the case.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This removes the need for the old helper entirely
|
| | | | |
| | | |
| | | |
| | | | |
This leverages Discord's new forum chanel feature, which removes the need for a lot of our custom logic, simplifying the help channel cog significantly.
|
| | | | | |
|
| | |/ / |
|
| | |/ |
|
| | |
| |
| | |
* Edited several tags
|
| | | |
|
| | | |
|