| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
| |
| |
| |
| | |
* Add founders role to constants.py
* Add Founders to some talentpool commands
|
| | |
|
|\ \
| | |
| | | |
Remove pings when auto-banning in filters
|
|/ /
| |
| |
| | |
Mods no longer want to be pinged when a fitler results in an auto ban, but we still want the message to be sent to mod-alerts.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [getsentry/action-release](https://github.com/getsentry/action-release) from 1 to 3.
- [Release notes](https://github.com/getsentry/action-release/releases)
- [Changelog](https://github.com/getsentry/action-release/blob/master/CHANGELOG.md)
- [Commits](https://github.com/getsentry/action-release/compare/v1...v3)
---
updated-dependencies:
- dependency-name: getsentry/action-release
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Added the possibility of slicing for the zen command
* Fixed off-by-one error, as the end index can be equal to the length of the zen
* Added support for negative signs and replaced re.search by re.match
* Allows for end_index == len(zen_lines). Previously, in that case, end_index % zen_lines would be 0, even though it's the last line
* Allows for slicing without a specified end index (e.g. "1:" will return all lines from the second to the last)
* Update end index display when slicing in the zen command
Co-authored-by: Vivek Ashokkumar <[email protected]>
* Added tests for the zen command
---------
Co-authored-by: Vivek Ashokkumar <[email protected]>
Co-authored-by: ChrisJL <[email protected]>
|
| |\ \
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Button for others to opt-in to be notified for reminders
|
| |\ \ \
| |/ / /
|/| | | |
|
| |_|/
|/| | |
|
| |\ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This removes the need of any form of error handling from `embeds` list
indexing, and makes the code more concise and readable.
The drawback is that a whole new embed object have to be allocated each
time, rather than editing the description like before.
|
| | |
| | |
| | |
| | |
| | | |
- More resilient handling of API errors.
- Don't rely on string manipulation to disable the button.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This solves most, if not all issues from the previous commit.
- A timeout of 5 minutes is enforced - this means the button can no
longer be used either when the reminder arrives or 5 minutes passes
since creation, whichever comes first.
- Reminder edits in between creation and button clicks will be handled
responsibly
- This includes both edits of duration, mentions, and deleting
reminders altogether.
- UX is improved. This list of to-be-mentioned users is sent up-front
with the author included. Instructions to click the button comes right
after the list.
- No updates to the API or site schema required, as the button message
will disable itself when it encounters any sort of errors.
- Implementation is also somewhat simplified.
There are probably more improvements, maybe one caveat, but it's like
almost midnight and I want to sleep :/ I sure hope the list above covers
most of it.
Further testing will be done. Now `.remind 10s test` is ingrained in my
muscle memory...
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the initial implementation - it's currently _far_ from perfect
and is very susceptible to errors.
Notable features beyond the basic requirements:
- Fails safely when max mentions reached (we're limited by the
2000-character limit when sending the reminder with the pings), and
disables the button.
- Adds an additional embed to the initial confirmation message to show
who clicked on the notify button.
- Edits the additional embed and disables the button when the reminder
is sent.
In many ways, this implementation is quite bad:
- Uses an async callback to delegate the task of PATCH-ing the API to
edit mentions to the `new_reminders` method.
- Edits to the opt-in list embed relies on the fact that the reminder is
not edited (using !remind edit) before someone clicks on the button. A
trivial way to fix this would be to add another field to the site
schema to store the `notification_view` in some way.
- The button is neither disabled nor any edits to the embed made when
the reminder is deleted before someone clicks on the button.
- String splitting is used which relies on the exact format of the embed
message when editing the embed to disable the button. We have to
reminder to update this piece of code when adjusting its format in the
future.
The UX can also be improved. Currently, I can't think of a way to
concisely phrase the button embed message so that it is clear that the
button is for people _other than_ the reminder author.
Notes:
- Max reminder mentions:
- Mentions are pinged directly in a discord message when the reminder
is sent. This means we're limited by the 2000-char limit. If we take
each User ID snowflake to be 18-characters, and considering each
mention to be formated as "<@ID> " (with extra space), it results in
about 90 mentions max. I've set the constant to 80 just in case.
- This is not an issue when the mentions are added in through other
means than the button we're adding in this commit, because the user
has to use @-mentions when sending the `!remind edit` command, which
is already under the discord's character limit.
- Log messages are added when something unexpected occurs within the
code. Hopefully this is unlikely to happen after the implementation
issues listed above are solved.
- The opt-in list in the second embed is separate from mentions added in
the original reminder creation, or any further edits, because mentions
are added by the to-be-mentioned-user, rather than by the reminder
author in this way. (Even though they are stored the same way.)
|
| | | |
|
| | |
| | |
| | | |
Co-authored-by: Vivek Ashokkumar <[email protected]>
|
| | |
| | |
| | |
| | | |
lines from the second to the last)
|
| | |
| | |
| | |
| | | |
% zen_lines would be 0, even though it's the last line
|
| | | |
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.11.12 to 3.11.13.
- [Release notes](https://github.com/aio-libs/aiohttp/releases)
- [Changelog](https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst)
- [Commits](https://github.com/aio-libs/aiohttp/compare/v3.11.12...v3.11.13)
---
updated-dependencies:
- dependency-name: aiohttp
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [pydantic-settings](https://github.com/pydantic/pydantic-settings) from 2.8.0 to 2.8.1.
- [Release notes](https://github.com/pydantic/pydantic-settings/releases)
- [Commits](https://github.com/pydantic/pydantic-settings/compare/v2.8.0...v2.8.1)
---
updated-dependencies:
- dependency-name: pydantic-settings
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.9.7 to 0.9.9.
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](https://github.com/astral-sh/ruff/compare/0.9.7...0.9.9)
---
updated-dependencies:
- dependency-name: ruff
dependency-type: direct:development
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
| |
| |
| |
| | |
This upgrade is suspected to cause the error with the cogs cog we were seeing in #dev-log.
E.G. https://discord.com/channels/267624335836053506/622895325144940554/1344409315556986991
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Bump deps to latest
* Sort deps
* Use new style group for dev deps
* Add attrs to ignore list of pip-licenses
* Bump bot-core up to 11.6.0
|
| |
| |
| | |
Security updates will always open PRs
|
|\ \
| | |
| | |
| | |
| | | |
dd2480-spring-2025-group-1/kim/test-cases-for-bot-utils-helpers
fix: `has_lines` returns empty str instead of bool
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Permit !remindme with no specified content
|
| | | |
| | | |
| | | |
| | | | |
content
|
| |/ /
| | |
| | |
| | | |
It's often desired to refer to the current discussion context without needing to explicitly write a placeholder
|
|/ / |
|
|\ \
| | |
| | | |
Swfarnsworth/fix auto upload
|
| |\ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
For some reason a thread with .closed=True was getting past this if statement.
See https://python-discord.sentry.io/issues/6281905188 and the value for post in the stack frame
|
| | |
| | |
| | |
| | | |
Previously, `on_message` used `Attachment.content_type.startswith("text")` for this, but this is false for some text-based files (like json).
|
| | | |
|
| | | |
|
| |\ \
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Help cog improvements
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
This ensures that the logic prior to closing also has the updated thread info
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Previously, (txt, csv, json, and py) files evoked special behavior from the filtering system. This is no longer the case.
|