| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Webhook URLs.
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
`scan_message` helper function to detect Webhook URL.
|
| | | | | | | | | | |
|
| |/ / / / / / / / |
|
| |\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | | |
Fix snekbox's message parsing to extract code for re-evaluation
|
| | |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Stuff like "{name} tried to run {command}" and
"{command} could not be found" was set as a warning,
and so Sentry issues were being created for these.
Our rule of thumb is that only actionable things should be warnings.
Changed these to Info logs.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Should return 1st arg (or None) if eval cmd in message, otherwise return
full content.
|
| |/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The previous parsing method was naïve in assuming there would always
be something preceding the code (e.g. the '!eval' command invocation)
delimited by a space. Now it will only split if it's sure the eval
command was used in the edited message.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Removed `zen` tag due `!zen` command exist.
|
| | |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Remove unused safety & dodgy dev dependencies
|
| |/ / / / / / / /
| | | | | | | |
| | | | | | | | |
Relock
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Update contributor doc
|
| | |\ \ \ \ \ \ \ \
| |/ / / / / / / /
|/| | | | | | | | |
|
| | | | | | | | | | |
|
| | | | |_|/ / / /
| | |/| | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Co-Authored-By: Mark <[email protected]>
|
| | | | |_|/ / /
| | |/| | | |
| | | | | | |
| | | | | | | |
Log message still used the first regex result (re.search) rather than the expanded approach (re.findall) recently added.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Partial hits may cause issues when packages get removed. The cache will
get bloated with packages which are no longer needed. They will keep
accumulating as more packages get removed unless the cache is unused for
7 days and gets automatically deleted by Azure Pipelines. Lingering
packages are also a potential cause for conflicts (e.g. unused package x
depends on package y==4.0 and useful package z depends on y==5.0).
Removing support for partial hits means all dependencies will be
installed whenever a single dependency changes.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
"python" is a shorter and clearer name.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Prevents the following error:
Can not perform a '--user' install. User site-packages are not visible
in this virtualenv.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Some of pipenv's dependencies overlap with dependencies in the Pipfile.
When installing from the Pipfile, any dependencies already present in
the global site will not be installed again to the user site, and thus
will not be cached. Therefore, pipenv is installed to the user site to
ensure all dependencies get cached.
* Move PATH prepend step before pipenv invocation
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Reduces frequency of using pipenv to install dependencies in CI. Works
by caching the entire Python directory. Only a full cache hit will
skip the pipenv steps; a partial cache hit will still be followed by
using pipenv to install from the pipfiles.
* Disable pip cache
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Makes the script for the coverage step cleaner.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The edit causes two channel update events to dispatch simultaneously:
one for the channel topic changing and one for the category changing.
The ModLog cog currently doesn't support ignoring multiple events of
the same type for the same channel. Therefore, the ignore was hard coded
rather than using the typical ignore mechanism.
This is intended to be a temporary solution; it should be removed once
the ModLog is changed to support this situation.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | | |
Co-Authored-By: Leon Sandøy <[email protected]>
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
There is no longer a reliance on static alphabetical position numbers.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When a channel is moved, all channels below have their positions
incremented by 1. This threw off the previous implementation which
relied on position numbers being static.
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Resetting a specific permission still keeps the overwrite for the member
around despite having default values. These will accumulate over time so
they should be completely removed once the permission needs to be reset.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This was happening when attempting to schedule a task twice for a user.
Because the scheduler refuses to schedule a duplicate, the coroutine
is deallocated right away without being awaited (or closed explicitly
by `scheduled_task`).
To fix, any existing task is cancelled before scheduling. This also
means if somehow a user bypasses the lack of permissions, their
cooldown will be updated. However, it probably doesn't make a difference
as if they can bypass once, they likely can bypass again.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Explicitly close the callback if it's a coroutine.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Can rely on `__str__` already being a channel's name.
|