| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Role was being accessed like a class when it is actually a dict.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The whole sync is aborted when an error is caught for simplicity's sake.
The sync message is edited to display the error and the traceback is
logged. To distinguish an error from an abort/timeout, the latter now
uses a warning emoji while the former uses the red cross.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
One is responsible for sending the confirmation prompt while the other
waits for the reaction. The split allows for the confirmation prompt
to be edited with the results of automatic syncs too.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This makes it clearer to users where the notification came from.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* Ignore bot reactions
* Check for core dev role if sync is automatic
* Require author as an argument to _confirm() so it can be compared
against the reaction author
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* Mention possibility of timing out as a reason for aborting a sync
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
It doesn't play along well with NamedTuple due to metaclass conflicts.
The workaround involved created a NamedTuple-only base class, which
does work but at the cost of confusing some static type checkers.
Since Diff is now an internal data structure, it no longer really needs
to have precise type annotations. Therefore, a normal namedtuple is
adequate.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The interface was becoming cumbersome to work with so it was all moved
to a single location. Now just calling Syncer.sync() will take care of
everything.
* Remove Optional type annotation from Diff attributes
* _confirm() can edit the original message and use it as the prompt
* Calculate the total diff and compare it against the max before
sending a confirmation prompt
* Remove abort message from sync(); _confirm() will handle that
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The confirmation prompt will be sent to the dev-core channel or the
specified context. Confirmation is done via reactions and waits 5
minutes before timing out.
* Add name property to Syncers
* Make _get_diff private; only sync() needs to be called now
* Change spelling of synchronize to synchronise
* Update docstrings
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Replaces the functions with a class for each syncer. The classes
inherit from a Syncer base class. A NamedTuple was also created to
replace the tuple of the object differences that was previously being
returned.
* Use namedtuple._asdict to simplify converting namedtuples to JSON
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* Use ID from constants directly instead of SYNC_SERVER_ID
* Use f-strings instead of %s for logging
* Fit into margin of 100
* Invert condition to reduce nesting
* Use Any instead of incorrect function annotation for JSON values
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Reduces code redundancy.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This seems to have been the intent of the original implementation.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
It has a much better guarantee that the cache will be available.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This coroutine waits until the configured guild is available and
ensures the cache is present.
The on_ready event is inadequate because it only waits 2 seconds for a
GUILD_CREATE gateway event before giving up and thus not populating the
cache for unavailable guilds.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Since the bot is now using Python 3.8 and some of our dependencies have Python-version specfic dependencies, it's important that the CI, which installs from our Pipfile, uses the same version of Python.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
One of the test_time methods did not actually assert the exception message it was trying to detect as the assertion statement was contained within the context manager handling the exception. I've moved it out of the context so it actually runs.
I've also added a few `praga: no cover` comments for parts that were artifically lowering coverage of the test suite.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Python 3.8 introduced an `unittest.mock.AsyncMock` class that can be used to mock coroutines and other types of asynchronous operations like async iterators and async context managers. As we were using our custom, but limited, AsyncMock, I have replaced our mock with unittest's AsyncMock.
Since Python 3.8 also introduces a different way of automatically detecting which attributes should be mocked with an AsyncMock, I've changed our CustomMockMixin to use this new method as well. Together with a couple other small changes, this means that our Custom Mocks now use a lazy method of detecting coroutine attributes, which significantly speeds up the test suite.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
I forgot to remove one pytest test file during the migration from pytest to unittest. Since we have sinced added a unittest version of the same file, I've now removed the lingering pytest file.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Since we upgraded to Python 3.8, we can now use the new IsolatedAsyncioTestCase test class to use coroutine-based test methods instead of our own, custom async_test decorator. I have changed the base class for all of our test classes that use coroutine-based test methods and removed the now obsolete decorator from our helpers.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We used inheritence to add additional logging assertion methods to unittest's TestCase class. However, with the introduction of the new IsolatedAsyncioTestCase this extension strategy means we'd have to create multiple child classes to be able to use the extended functionality in all of the TestCase variants.
Since that leads to undesirable code reuse and an inheritance relationship is not at all needed, I've switched to a mixin-composition based approach that allows the user to extend the functionality of any TestCase variant with a mixin where needed.
|
| | |_|_|_|_|_|/
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
I've changed the Python version in our Pipfile to Python 3.8. The main advantage of Python 3.8 is that it comes with significant upgrades to the unittest module which allow us to test asyncio-based code more easily. While our current test suite runs in P3.8 "out of the box", it currently still relies on many of the workarounds we had to use to test asynchronous code in Python 3.7. A future commit will replace these workarounds with the new tools available in Python 3.8.
This commit also updates our discord.py version to 1.3.2. Versions of discord.py <= 1.3.1 contain a bug that causes errors in the new unittest tools that come with Python 3.8. For more specific details, see https://github.com/Rapptz/discord.py/pull/2570.
|
| |\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
Reminder Embed Enhancements & Whitelist Expansion
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Check reminder user and channel before send and schedule.
|
| | |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Change verification post log level to info, tidy code.
|
| | |\ \ \ \ \ \ \ \
| |/ / / / / / / /
|/| | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Fix missing Django logs when using Docker Compose
|
| | |\ \ \ \ \ \ \ \ \ |
|
| | | |_|_|_|_|/ / / /
| |/| | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Fixed by allocating a pseudo-tty to the web and bot services in Docker
Compose.
|
| |\ \ \ \ \ \ \ \ \ \
| |_|/ / / / / / / /
|/| | | | | | | | | |
Reduce log level of tag cooldown notice.
|
| |/ / / / / / / / / |
|