| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Creating a new object caused the assert to fail because different objects were used.
|
| | |
|
| |
|
|
| |
`assert_called_once_with` was being tested on call_args which always reported success.st.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This allows us to use coroutines with await directly instead of asyncio.run
|
| | |
|
| |
|
|
| |
Before the channel was not added if `persistent` was `True`.
|
| |
|
|
|
|
| |
With the removal of the channel args,
it's no longer necessary to mention the channel in the command output.
Tests adjusted accordingly
|
| |
|
|
|
| |
Needless call args which were constant were kept in the test cases, resulting in redundant code,
the args were moved directly into the function call.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Previously silencing a channel reset all overwrites excluding `send_messages`
and unsilencing them removed all overwrites.
This is prevented by getting the current overwrite
and applying it with only send_messages changed.
|
| | |
|
| |
|
|
|
|
|
| |
Separating the notifier allows us to keep the Silence class
and its methods to be more focused on the class' purpose,
handling the logic of adding/removing channels
and the loop itself behind `SilenceNotifier`'s interface.
|
| | |
|
| |
|
|
|
| |
Calling the command coro directly did unnecessary checks and
made tests for the method harder to realize.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
FirstHash is used for handling channels in `loop_alert_channels` set as tuples without considering other elements.
|
| | |
|
| |\
| |
| | |
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
|
Numerlor
S. Co1
Leon Sandøy
kwzrd
Joseph
scragly
Spencer Young
S. Co1
Sebastiaan Zeeff
Eivind Teig
MarkKoz