| Commit message (Collapse) | Author | Age | Lines |
|---|
| |\ |
|
| | |\
| | |
| | | |
Prevent exception if a watched user sends a DM to the bot
|
| | |/
| |
| | |
The previous embed assumed that the messages would be sent on the server, where the channel would have a name and the message would have a jump URL. For a DM, neither of these are present and an exception will be raised when attempting to construct the embed for the webhook to send.
|
| | |\
| | |
| | | |
Create AsyncResolver inside a coroutine to avoid DeprecationWarning
|
| | | |\
| | |/
| |/| |
|
| | | |
| | |
| | | |
Co-Authored-By: Leon Sandøy <[email protected]>
|
| | | |\
| | | |
| | | |
| | | | |
bug/backend/b748/resolver-in-coro
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
"Real" warnings weren't showing up for some reason.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
aiohttp does warn too, but these warnings will provide more immediate
feedback.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Because discord.py recreates the HTTPClient session, may as well follow
suite and recreate our own stuff here too.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The function itself doesn't need to be a coroutine. It just has to be
called in a coroutine (or, more indirectly, in an async context?).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The client can be used without running a bot so it makes more sense
for the connector to be created when logging in, which is done in both
cases, rather than in start(), which is only used when running a bot.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
AsyncResolver has to be created inside a coroutine so it's moved
inside start(). Consequently, the APIClient session is also recreated
inside start() now.
When using clear(), the default connector is used for the session it
recreates because clear() is not a coroutine. This should only affect
requests made to the Discord API via the Client when not using it to run
a bot; starting the bot will re-create the session with the custom
connector.
* Close connector and resolver when bot closes
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These kwargs are merged with the kwargs given when the APIClient was
created. This is useful for facilitating changing the session's
connector with a new instance when the session needs to be recreated.
* Rename _session_args attribute to _default_session_kwargs
|
| | | | | |
|
| | | | |
| | | |
| | | | |
This was added by the now-removed Snake cog & is not used elsewhere on bot.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The mock gets used by the flake8 pre-commit hook, which invokes flake8
via `pipenv run flake8`. It's normally useful to use pipenv here cause
it ensures flake8 is invoked within the context of the venv. However, in
CI, there is no venv - dependencies are installed directly to the
system site-packages. `pipenv run` does not work in such case because it
tries to create a new venv if one doesn't exist (it doesn't consider the
system interpreter to be a venv).
This workaround (okay, it's a hack) creates an executable shell script
which replaces the original pipenv binary. The shell script simply
ignores the first argument (i.e. ignores `run` in `pipenv run`) and
executes the rest of the arguments as a command. It essentially makes
`pipenv run flake8` equivalent to just having ran `flake8`. When
pre-commit executes pipenv, the aforementioned script is what will run.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A cache for an outdated pre-commit environment may still be useful. It
may be the case that only some hooks need to be updated rather than
all.
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | | |
* Remove trailing whitespaces
* Specify error code for a noqa in the free command
|
| | | |
| | |
| | | |
Resolves an issue mentioned in https://github.com/python-discord/bot/issues/767, giving Helpers access to post invites and other things caught by the Filtering cog.
|
| |\ \ \
| | | |
| | | | |
Migrate bot to Python 3.8
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Add grabify (IP logger) domains to banned domains
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Optimize Dockerfile for faster rebuilds
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | | |
Previous regex utilized a `/`, which doesn't work for comparing against Windows paths, which use `\`
|
| | | | | |
| | | | |
| | | | | |
Returning directly out of a `finally` clause can cause any exceptions raised in the clause to be discarded, so we can remove the finally clause entirely and shift the control statements into the body of the function
|
| | | | | |
| | | | |
| | | | | |
* Remove explicit urllib3 pinning, CVE that caused its pinning has been resolved by 1.25+. This is a child dependency of requests.
|
| | | |\ \ \
| |_|/ / /
|/| | | |
| | | | | |
I have resolved a merge conflict in Pipfile.lock by relocking with the newly added dependencies of `coloredlogs` and `colorama`.
|
| |\| | | |
| | | | |
| | | | | |
Coloured log output
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
This makes it easy to add colour to the logs. Colorama is also installed
if on a Windows system.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I've migrated the `tests/test_snekbox.py` file to use the new Python 3.8-style unittests instead of our old style using our custom Async mocks.
In particular, I had to make a few changes:
- Mocking the async post() context manager correctly
Since `ClientSession.post` returns an async context manager when called, we need to make sure to assign the return value to the __aenter__ method of whatever `post()` returns, not of `post` itself (i.e.. when it's not called).
- Use the new AsyncMock assert methods `assert_awaited_once` and `assert_awaited_once_with`
Objects of the new `unittest.mock.AsyncMock` class have special methods to assert what they were called with that also assert that specific coroutine object was awaited. This means we test two things in one: Whether or not it was called with the right arguments and whether or not the returned coroutine object was then awaited.
- Patch `functools.partial` as `partial` objects are compared by identity
When you create two partial functions of the same function, you'll end up with two different `partial` objects. Since `partial` objects are compared by identity, you can't compare a `partial` created in a test method to that created in the callable you're trying to test. They will always compare as `False`. Since we're not interested in actually creating `partial` objects, I've just patched `functools.partial` in the namespace of the module we're testing to make sure we can compare them.
|
| | |\ \ \
| |/ / /
|/| | |
| | | | |
I've resolved the merge conflict by confirming the deleted part of tests/helpers.py
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
python-discord/bug/backend/b754/scheduler-suppresses-errors
Don't suppress all errors in scheduler
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix invalid tag names being passed to the tag cog.
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Eval cog improvements
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
It could have caused some errors if the user delete his own message
|
scragly
S. Co1
Mark
Leon Sandøy
S. Co1
kwzrd
Joseph
Spencer Young
Sebastiaan Zeeff
Eivind Teig
Shirayuki Nekomata
Matteo