| Commit message (Collapse) | Author | Lines |
|
Bumps [rapidfuzz](https://github.com/maxbachmann/RapidFuzz) from 2.15.0 to 2.15.1.
- [Release notes](https://github.com/maxbachmann/RapidFuzz/releases)
- [Changelog](https://github.com/maxbachmann/RapidFuzz/blob/main/CHANGELOG.rst)
- [Commits](https://github.com/maxbachmann/RapidFuzz/compare/v2.15.0...v2.15.1)
---
updated-dependencies:
- dependency-name: rapidfuzz
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
|
|
Bumps [coverage](https://github.com/nedbat/coveragepy) from 7.2.2 to 7.2.3.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](https://github.com/nedbat/coveragepy/compare/7.2.2...7.2.3)
---
updated-dependencies:
- dependency-name: coverage
dependency-type: direct:development
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
|
|
Bumps [beautifulsoup4](https://www.crummy.com/software/BeautifulSoup/bs4/) from 4.12.0 to 4.12.2.
---
updated-dependencies:
- dependency-name: beautifulsoup4
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
|
|
|
|
100 is the maximum number that can be received in one request, so we may as well use that many. Also change a string `+=` to `=`.
|
|
|
|
|
|
|
|
Additionally fixes the nickname filter not using the right object to take action and report.
|
|
|
|
This doesn't work at the moment with the new filtering and a proper fix will be made later
|
|
|
|
|
|
|
|
|
|
Bumps [rapidfuzz](https://github.com/maxbachmann/RapidFuzz) from 2.13.7 to 2.15.0.
- [Release notes](https://github.com/maxbachmann/RapidFuzz/releases)
- [Changelog](https://github.com/maxbachmann/RapidFuzz/blob/main/CHANGELOG.rst)
- [Commits](https://github.com/maxbachmann/RapidFuzz/compare/v2.13.7...v2.15.0)
---
updated-dependencies:
- dependency-name: rapidfuzz
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
|
|
|
This is to make sure that the unique constraint always compares between dicts instead of sometimes dealing with nulls.
|
|
Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.18.0 to 1.19.1.
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-python/compare/1.18.0...1.19.1)
---
updated-dependencies:
- dependency-name: sentry-sdk
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
Bumps [pre-commit](https://github.com/pre-commit/pre-commit) from 3.2.1 to 3.2.2.
- [Release notes](https://github.com/pre-commit/pre-commit/releases)
- [Changelog](https://github.com/pre-commit/pre-commit/blob/main/CHANGELOG.md)
- [Commits](https://github.com/pre-commit/pre-commit/compare/v3.2.1...v3.2.2)
---
updated-dependencies:
- dependency-name: pre-commit
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>
|
|
|
|
|
|
|
|
|
|
Also changes the alert to use the full domain instead of the filter content.
|
|
This is in response to recent attacks where the attacker DMs someone who opens a thread and tells the thread opener to pip install a malicious package under the false pretense that it will solve their problem. The warning replaces "For more tips, check out our guide on asking good questions", which is stated in the thread closer embed.
|
|
This shouldn't happen in production, but just in case
|
|
|
|
|
|
|
|
|
|
Add logic to see if anyone other than the OP (or bots) engaged in a help thread when it closes for inactivity. Currently only looks at the last 10 messages. If not, includes a ping to the OP before the embed in the closing message.
|
|
|
|
|
|
|
|
Previously, the message from the bot requesting that new helpers answer off-topic questions did not cause a ping. Solved by this commit.
|
|
|
|
Namely just seeing if there's a question mark in it that isn't part of a URL.
|
|
It may occasionally be confusing why the bot thinks people need to "help" if there's a false positive (ie if the message is not a question).
|