aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Fltering: clean up autoban codeGravatar Matteo Bertucci2021-10-25-4/+4
|
* Filter list: move warning to #mod-metaGravatar Matteo Bertucci2021-10-25-4/+4
|
* Merge remote-tracking branch 'origin/main' into filters/autobanGravatar Matteo Bertucci2021-10-25-303/+360
|\
| * Merge pull request #1908 from python-discord/fix-tz-issueGravatar Hassan Abouelela2021-10-23-2/+5
| |\ | | | | | | Use datetime.fromtimestamp so we pass relativedelta a datetime object…
| | * Use datetime.fromtimestamp so we pass relativedelta a datetime object, not ArrowGravatar Chris Lovering2021-10-22-2/+5
| |/ | | | | | | | | Fixes #1907 Fixes BOT-1PA
| * Merge pull request #1906 from python-discord/fix-tzinfo-issueGravatar Hassan Abouelela2021-10-23-2/+2
| |\ | | | | | | Use Arrow.fromtimestamp to get an aware datetime
| | * Use Arrow.fromtimestamp to get an aware datetimeGravatar Chris Lovering2021-10-22-2/+2
| |/ | | | | | | | | | | | | Fixes #1905 Fixes BOT-1P9 datetime.fromtimestamp returned an naive datetime, so when comparing to the aware datetime from dateutil.parser.isoparse, it would raise an error.
| * Move to timezone aware datetimes (#1895)Gravatar Boris Muratov2021-10-22-113/+122
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Move to timezone aware datetimes With the shift of the discord.py library to timezone aware datetimes, this commit changes datetimes throughout the bot to be in the UTC timezone accordingly. This has several advantages: - There's no need to discard the TZ every time the datetime of a Discord object is fetched. - Using TZ aware datetimes reduces the likelihood of silently adding bugs into the codebase (can't compare an aware datetime with a naive one). - Our DB already stores datetimes in UTC, but we've been discarding the TZ so far whenever we read from it. Specific places in the codebase continue using naive datetimes, mainly for UI purposes (for examples embed footers use naive datetimes to display local time). * Improve ISODateTime converter documentation Co-authored-by: Kieran Siek <[email protected]>
| * Merge pull request #1904 from python-discord/modlog/explicit-thread-nameGravatar ChrisJL2021-10-22-3/+12
| |\ | | | | | | Modlog: explicitly write thread names
| | * Modlog: explicitly write thread namesGravatar Matteo Bertucci2021-10-22-3/+12
| |/ | | | | | | It seems like there could be some caching issue with threads causing to appear as deleted channels. Beside, we also want to keep the name of deleted threads around.
| * Merge pull request #1902 from python-discord/bump-licensesGravatar Matteo Bertucci2021-10-21-88/+95
| |\ | | | | | | Bumps Pip Licences
| | * Bumps Pip LicencesGravatar Hassan Abouelela2021-10-22-88/+95
| |/ | | | | | | | | | | | | Updates the pip-licences version to fix a breaking bug in the currently pinned version. Signed-off-by: Hassan Abouelela <[email protected]>
| * Merge pull request #1897 from python-discord/modlog/correct-color-namesGravatar Karlis Suvi2021-10-20-4/+4
| |\
| | * Modlog: correct color namesGravatar Matteo Bertucci2021-10-19-4/+4
| |/ | | | | Solves https://github.com/python-discord/bot/issues/1896
| * Merge pull request #1894 from python-discord/modlog-soft-colorsGravatar ChrisJL2021-10-19-4/+4
| |\ | | | | | | Mod-log thread: use soft colors
| | * Mod-log thread: use soft colorsGravatar Matteo Bertucci2021-10-19-4/+4
| |/ | | | | Seems like we have been using the wrong colors in mod-log.
| * Merge pull request #1845 from python-discord/fix-sentry-BOT-1N6Gravatar Matteo Bertucci2021-10-19-6/+13
| |\ | | | | | | Handle edge case of `message.author` being a `discord.User` when claiming a help channel.
| | * Merge branch 'main' into fix-sentry-BOT-1N6Gravatar TizzySaurus2021-10-19-981/+1567
| | |\ | | |/ | |/|
| * | Merge pull request #1890 from python-discord/Migrate-to-socket_event_typeGravatar Matteo Bertucci2021-10-18-4/+3
| |\ \ | | | | | | | | Migrate to on_socket_event_type event
| | * | Migrate to on_socket_event_type eventGravatar Chris Lovering2021-10-18-4/+3
| |/ / | | | | | | | | | | | | | | | | | | | | | Discord.py 2.0 (Namely this commit https://github.com/Rapptz/discord.py/commit/e2250d402e8ad035b2653eb411c8e744cc9eb3bf) removed the socket_response event, and replaced it with the socket_event_type event, which just sends the type of event triggered on the websocket. Since this event was removed, no socket stats were being incremented, as the event never triggered. I have looked through the rest of the bot, and we do not use the socket_response event type anywhere else.
| * | Fix guild icon URL getting way in server command (#1888)Gravatar Karlis Suvi2021-10-17-1/+1
| | |
| * | Merge pull request #1887 from python-discord/fix-guild-attr-errorGravatar Karlis Suvi2021-10-17-1/+1
| |\ \ | | | | | | | | Fix attr error since asset attrs have changed in 2.0
| | * | Fix attr error since asset attrs have changed in 2.0Gravatar Chris Lovering2021-10-17-1/+1
| |/ / | | | | | | | | | | | | | | | | | | Fixes #1886 Fixes BOT-1NZ This was updated with Discord.py 2.0.
| * | Merge pull request #1885 from python-discord/fix-files-being-sent-in-webhooksGravatar Boris Muratov2021-10-17-1/+1
| |\ \ | | | | | | | | Use MISSING sentinal rather than None for no files
| | * | Use MISSING sentinal rather than None for no filesGravatar Chris Lovering2021-10-17-1/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | Fixes #1884 Fixes BOT-1NY Discord.py 2.0 changed how this works, webhooks now look for the MISSING sentinal, rather than None to determine whether files are being passed. This was updated in this commit: https://github.com/Rapptz/discord.py/commit/a6f7213c89e9d592c69ea3c631b0cb2bdab19577
| * | Merge pull request #1844 from python-discord/new-appeals-processGravatar Matteo Bertucci2021-10-17-20/+20
| |\ \ | | | | | | | | Direct users to the appeals server when banned
| | * \ Merge branch 'main' into new-appeals-processGravatar ChrisJL2021-10-17-954/+1541
| | |\ \ | | |/ / | |/| |
| * | | Merge pull request #1882 from python-discord/fix-attr-errorGravatar Karlis Suvi2021-10-17-1/+1
| |\ \ \
| | * | | Fix attr error in ModLog commandGravatar Chris Lovering2021-10-17-1/+1
| |/ / / | | | | | | | | | | | | | | | | Fixes #1881 Fixes BOT-1NX
| * | | Merge pull request #1795 from Numerlor/doc-repetitive-outdated-warnGravatar wookie1842021-10-17-19/+47
| |\ \ \ | | | | | | | | | | Prevent repetitive stale inventory warnings from erroneously generated inventories
| | * \ \ Merge branch 'main' into doc-repetitive-outdated-warnGravatar wookie1842021-10-17-1074/+1816
| | |\ \ \ | | |/ / / | |/| | |
| * | | | Fixed delayed logs and made some other minor refactors (#1863)Gravatar wookie1842021-10-17-28/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Run debug log before help command invocation to avoid delayed logs * Refactored other areas of code slightly, ensuring logging is done as soon as possible. Removed outdated comment * Ensured debug logs were sent for disabled commands Co-authored-by: Xithrius <[email protected]>
| * | | | Regex: add a word boundary before .gg (#1817)Gravatar Matteo Bertucci2021-10-17-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Regex: add a word boundary before .gg and use named groups Before this commit, `an-arbitrary-domain.gg/notaninvite` would trigger the filter. This solve the issue by adding a word boundary before this branch of the pattern. * Regex: replace the word boundary by a word char Co-authored-by: ChrisJL <[email protected]> Co-authored-by: ChrisJL <[email protected]> Co-authored-by: Xithrius <[email protected]>
| * | | | Merge pull request #1876 from python-discord/fix-help-description-spacingGravatar wookie1842021-10-17-1/+5
| |\ \ \ \ | | | | | | | | | | | | Formats Help Command Output
| | * \ \ \ Merge branch 'main' into fix-help-description-spacingGravatar wookie1842021-10-17-14/+24
| | |\ \ \ \ | | |/ / / / | |/| | | |
| | * | | | Formats Help Command OutputGravatar Chris Lovering2021-10-17-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #1232 Modifies the docstring sent for per-command help to remove weird formatting issues mentioned in #1232. Removes newlines that are not used for paragraph breaks, after retrieving the docstring, and lets the embed handle it on the discord side. Allow overriding this behaviour via \u2003 to denote a non-escapable break. Co-authored-by: Hassan Abouelela <[email protected]>
| | | * | | Raise for status to prevent parsing of invalid pagesGravatar Numerlor2021-08-31-1/+1
| | | | | |
| | | * | | Delete stale item counters when clearing doc cacheGravatar Numerlor2021-08-30-0/+13
| | | | | |
| | | * | | Prevent erroneous symbols from always raising stale warningsGravatar Numerlor2021-08-30-7/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some doc symbols are improperly generated and never exist on the doc page the inventory file defines them in, causing the stale warning to get raised every time the page is parsed (at a maximum every week because of the redis expire). This can be prevented by keeping a counter in redis for the items which were stale, every time the item is warned for the counter is incremented and set to expire in 3 weeks. Then a warning is only raised when the counter is below 3, resulting in the unpreventable warning only being raised twice until it is fixed by the maintainers after it expires in 3 weeks after the last increment.
| | | * | | create a helper function to get the redis key of a doc itemGravatar Numerlor2021-08-30-12/+5
| | | | | |
| | | | * | Update infraction DM tests to reflect new outputGravatar Chris Lovering2021-09-24-10/+10
| | | | | |
| | | | * | Direct users to the appeals server when bannedGravatar Chris Lovering2021-09-24-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a new appeals process we are trialing. Users who get banned join this server and DM a modmail bot, who relays the message to the main server for mods to discuss. I have updated the shortening logic to allow for extra information to be included at the end of the embed, while still staying under the limit.
| | | | | * Update log message for when author isn't `discord.Member`Gravatar Izan2021-10-19-2/+1
| | | | | |
| | | | | * Invert `isinstance` check as per reviewGravatar Izan2021-10-19-3/+6
| | | | | |
| | | | | * Add handling for when `message.author` is a `discord.User`Gravatar Izan2021-09-24-6/+11
| | | | |/ | | | | | | | | | | | | | | | NB: Will give a sentry warning when this happens.
* | | | | Filter list: send warning when autoban trigger is addedGravatar Matteo Bertucci2021-10-25-2/+11
| | | | |
* | | | | Filtering: update auto ban messageGravatar Matteo Bertucci2021-10-25-3/+15
| | | | |
* | | | | Infrac: prioritize mod over bot feedback msgGravatar Matteo Bertucci2021-10-25-8/+8
| | | | |
* | | | | Filtering: make autoban tempGravatar Matteo Bertucci2021-10-19-8/+4
| | | | |
* | | | | Filtering: do not try to convert to a memberGravatar Matteo Bertucci2021-10-19-2/+2
| | | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-30 08:00:44 +0000