|  | Commit message (Collapse) | Author | Age | Lines | 
|---|
| ... |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | modified .mars command result check, some very small fixes. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | for it) and moved all what this do to .nasa command. | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | and/or space | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | (upcoming) .nasa command. | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | NASA API and support arguments endpoint and params. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | parameters | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | | Changed `hours` argument in `refresh_genres_task` from `1.0` to `24.0` due no need for so fast updating. | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | matching in `.games` command. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | that have higher than 0.60 ratio. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | correct genres. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | This way, we can standardize the way Months are shown to both the user
and the developer. Note that if passing a Month member to an f-string,
the `!s` format code must be specified to ensure our __str__ is used.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Previously, the `should_cycle` iterator would signal that it is time
to cycle by yielding True. As per Mark's suggestion, this is adjusted
to yield either None, or ints representing days since last cycle.
This is more transparent, as the daemon can now perform the comparison
against the configured cycle frequency itself, rather than relying
on being fed the correct value from a "black box".
See `_reset_should_cycle` docstring for further clarification.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Add a static check confirming that no seasons overlap. This avoids
having to deal with ambiguities in `get_current_season` at runtime,
as we can now rely on `len(active_seasons)` always being 0 or 1.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | For the sake of consistency - all other seasonal bot names have
the B capitalized.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | With the 'seasonal-structure' branch being merged in the branding
repository, we can start polling master. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | After 00af207de3087a41270f216ad86e06ba7dbf9d42, we should ensure that
the month names aren't shown to the user in all caps.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | It is not necessary for these to be coroutines.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | This should be more readable.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Reduces code duplication.
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | * Capitalize month names
* Add backticks to `sha` attr reference
* Avoid misusing the term 'poll'
Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Co-authored-by: MarkKoz <[email protected]> | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Previously, the env var was only being used for seasonal decorators,
not branding. Although for testing purposes, seasons can be easily
set via bot commands, it makes sense to also use the env var to
choose the current season. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | The function is useful to other modules as well - not only decorators.
This declares it as public and moves it to a more accessible place. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Constant is no longer used.
See: 9259f985e6e327a522b4420c879a50cb4f75a09d | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | A persistent config file will remember whether the daemon is supposed
to be running, or not. This means that instead of relying on the env
variable, the daemon can be turned on or off "once and for all"
via a command, and will not violate this decision on restart.
This effectively deprecates the `Branding.autostart` env var. It is
believed that having two ways to configure the same thing would
be more confusing than useful. The env var will be removed.
The two helper functions for reading and writing have been implemented
in a generic manner, meaning that should a new config key be added in
the future, the helpers shouldn't require any further adjustments.
Suggested by lemon and scragly.
Co-authored-by: Leon Sandøy <[email protected]>
Co-authored-by: scragly <[email protected]> | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | See docstring for details. | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | The diff should demonstrate how much code repetition we prevent.
We do not make use of `_apply_asset` for nickname changes - due to
the comparative simplicity and conceptual difference, this method
provides its own error handling. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Current `set_avatar`, `set_icon` and `set_banner` methods are almost
identical - they only differ in the type of asset they upload. This
leads to a lot of code repetition, especially w.r.t. error handling.
We instead add a generic method that is parametrized by an AssetType
param, and by the target entity (i.e. bot, or guild) that the asset
should be applied to. All error handling can then be done in one place.
Error handling methodology is adjusted - instead of suppressing errors,
we catch and log them. Since we no longer determine whether the upload
succeeded based on 'before' != 'after', this solves a bug where
re-applying the same asset resulted in a warning-level log, triggering
Sentry. | 
| | | | | | | |  | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | It is not necessary to log all icon paths on each shuffle. Creates
unnecessary visual clutter in the logfile. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | The method is a left-over from the old seasonal system. We no longer
use it, the bot's username never changes, only the nickname.
The amount of internal branching logic makes it difficult to maintain. | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | | Define commands in the same order in which the cog's docstring lists
them. This shall make it easier to browse or look up implementations.
The commands are defined roughly in the order in which a user would be
expected to use them. |