aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| * | | | | | Added dynamic available help channels messageGravatar xithrius2021-02-04-0/+48
| | | | | | |
| * | | | | | Added how_to_get_help constant.Gravatar xithrius2021-02-04-0/+2
| | | | | | |
| | * | | | | "handle converting" -> "convert ... for you". Gravatar Steele Farnsworth2021-02-06-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Per Gustav's suggestion. Co-authored-by: Gustav Odinger <[email protected]>
| | * | | | | Removed extra blank line. Gravatar Steele Farnsworth2021-02-06-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It added more vertical white space than was wanted. Co-authored-by: Gustav Odinger <[email protected]>
| | * | | | | New example to emphasize the mapping functionality rather than filtering.Gravatar swfarnsworth2021-02-06-9/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the example only conveyed how the `if` statement of list comps could be used to filter a list, whereas the mapping functionality is what people primarily use list comps for.
| | * | | | | More robust example with no reference to Python versions or `str.format`.Gravatar swfarnsworth2021-02-06-14/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The example emphasizes that you can evaluate expressions in the curly braces. Python 3.5 has already reached EOL, so anyone who doesn't have f-strings at this point is probably running 2.7 anyway. I also removed the information about `str.format` to reduce the scope.
| | * | | | | Rewrite to use simpler examples.Gravatar swfarnsworth2021-02-06-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous examples might have been confusing for some readers. I also removed the part about inverting a dict because I think that's out of scope and would require more explanation given all the consequences that could have.
| | | | * | | Merge branch 'mbaruh/defcon' of https://github.com/python-discord/bot into ↵Gravatar mbaruh2021-03-02-12/+19
| | | | |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | mbaruh/defcon
| | | | | * | | Provide default cache values when syncingGravatar Boris Muratov2021-03-01-2/+2
| | | | | | | |
| | | | | * | | Change to handle specifically redis errorsGravatar Boris Muratov2021-03-01-11/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea to ignore alerts on fake redis didn't solve the problem completely, because sometimes you'll just develop with a real redis. It also didn't solve the ping we would get on first start up. After looking into it there seems like there's no actual reason to alert on key errors, as they should only happen if the cache gets wiped for some reason, which shouldn't happen, but in which case we have bigger issues. Alerts are therefore limited to connection errors raised by redis. This additionally handles only redis errors when writing to it as well. If any other error is raised it is ok for the function to stop at that point, as all variables have already been set. The only thing which doesn't get executed is the confirmation message and logging, the lack of which is an exception message in itself.
| | | | | * | | Sync alert won't trigger with fake redisGravatar Boris Muratov2021-02-26-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The alert will trigger with fake redis on every bot startup even when people aren't working on the defcon cog. Added a condition to check if fake redis is being used.
| | | | | * | | Changed name of _duration_parser constant to uppercaseGravatar Boris Muratov2021-02-26-2/+2
| | | | | | | |
| | | | | * | | Supressing any exceptions while updating the threshold in redisGravatar Boris Muratov2021-02-26-6/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating redis might cause an error, making sure it doesn't stop the command mid-way
| | | | * | | | Improved docstring for threshold command.Gravatar mbaruh2021-03-02-1/+8
| | | | |/ / /
| | | | * | | Retain 'd' alias for threshold commandGravatar mbaruh2021-02-19-1/+1
| | | | | | |
| | | | * | | Error to load settings will send the traceback to the channelGravatar mbaruh2021-02-19-0/+2
| | | | | | |
| | | | * | | Threshold has false-y value when set to 0Gravatar mbaruh2021-02-17-15/+20
| | | | | | |
| | | | * | | Error loading settings will also ping devops roleGravatar mbaruh2021-02-17-1/+5
| | | | | | |
| | | | * | | Gave more meaningful name and description to the cacheGravatar mbaruh2021-02-17-5/+8
| | | | | | |
| | | | * | | Changed server command to work with new defcon cogGravatar mbaruh2021-02-17-6/+7
| | | | | | |
| | | | * | | Renamed _defcon_action to _update_threshold and updated docstringGravatar mbaruh2021-02-14-4/+4
| | | | | | |
| | | | * | | Removed cog check, shutdown restricted to adminsGravatar mbaruh2021-02-14-4/+5
| | | | | | |
| | | | * | | _update_channel_topic not longer needs to be awaitedGravatar mbaruh2021-02-14-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It's important to note that it's appropriate for the sync and action methods to have a lock between them, because if an action is made before syncing is complete it gets screwed and starts throwing excpetion for every command.
| | | | * | | Prevent channel description edit from locking commandsGravatar mbaruh2021-02-13-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Because some parts are defined as atomic transaction, we can't use them with channel description edits which are heavily rate limited. Description edits are now run in a separate task.
| | | | * | | Status command displays verification levelGravatar mbaruh2021-02-13-0/+1
| | | | | | |
| | | | * | | Fixed on_messageGravatar mbaruh2021-02-13-8/+11
| | | | | | |
| | | | * | | Add option to schedule threshold resetGravatar mbaruh2021-02-13-16/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Added optional argument to defcon threshold to specify for how long it should be on. The notifier will now run only when there is no expiry date specified.
| | | | * | | Defcon days is now defcon threshold with DurationDeltaGravatar mbaruh2021-02-13-41/+84
| | | | | | |
| | | | * | | Added cog check to only allow mods in the defcon channelGravatar mbaruh2021-02-13-5/+4
| | | | | | |
| | | | * | | Removed _build_defcon_message methodGravatar mbaruh2021-02-13-24/+15
| | | | | | |
| | | | * | | Added server shutdown and reopen commandsGravatar mbaruh2021-02-13-2/+24
| | | | | | |
| | | | * | | Reordered methodsGravatar mbaruh2021-02-13-18/+18
| | | | | | |
| | | | * | | Removed enabling and switched to redisGravatar mbaruh2021-02-13-132/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Removing self.enable and the defon & defoff commands. Defcon will now just be always 'on' and we can set the days threshold to 0 to turn it off. Switched from postgres to redis - if the data gets lost we should just reconfigure defcon again, it should not depend on the site.
| | | | * | | Defon doesn't reset the number of daysGravatar Boris Muratov2021-01-26-1/+1
| | | | | | |
| | | | * | | Merge branch 'mbaruh/defcon' of https://github.com/python-discord/bot into ↵Gravatar Boris Muratov2021-01-26-3222/+4337
| | | | |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | mbaruh/defcon
| | | | | * \ \ Merge branch 'master' into mbaruh/defconGravatar Boris Muratov2021-01-26-3222/+4337
| | | | | |\ \ \ | | | |_|_|/ / / | | |/| | | | |
| | | | * | | | Added cog unloader to cancel notifierGravatar Boris Muratov2021-01-26-0/+8
| | | | | | | |
| | | | * | | | Moved channel topic change to _defcon_actionGravatar Boris Muratov2021-01-26-3/+1
| | | | | | | |
| | | | * | | | Moved self.enabled update to _defcon_actionGravatar Boris Muratov2021-01-26-9/+6
| | | | | | | |
| | | | * | | | Make the cog update even if write to DB failsGravatar Boris Muratov2021-01-26-3/+3
| | | | |/ / / | | | | | | | | | | | | | | | | | | | | | The defcon cog should be functional even if there is some issue with writing to the DB for some reason. The functionality should have retention across restarts, but it shouldn't be its failing point. If necessary, it should be able to work with no DB at all
| | | | * | | Added defcon status notifierGravatar mbaruh2020-10-30-1/+22
| | | | | | |
| | | | | * | GrammarGravatar Chris2021-01-31-1/+1
| | | | | | |
| | | | | * | return true when tag is on cdGravatar Chris2021-01-31-3/+4
| | | | | | |
| | | | | | * Remove compatibility-none returns from filtersGravatar ks1292021-02-24-27/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This doesn't look good to have just None returns, so made changes so if function don't return tuple, then reason is automatically None.
| | | | | | * Move reason for guild filtering to footerGravatar ks1292021-02-20-3/+2
| | | | | | |
| | | | | | * Add comments about returning blacklist entry reasons to filtersGravatar ks1292021-02-17-3/+18
| | | | | | |
| | | | | | * Rename filter trigger reason from entry command to reasonGravatar ks1292021-02-17-2/+2
| | | | | | |
| | | | | | * Add missing None reason returns of filtersGravatar ks1292021-02-17-3/+3
| | | | | | |
| | | | | | * Implement showing filterlist entry comment in alertsGravatar ks1292021-02-06-23/+40
| |_|_|_|_|/ |/| | | | |
* | | | | | Merge pull request #1397 from python-discord/feat/1280/deleted-jumplinkGravatar Senjan212021-02-05-0/+2
|\ \ \ \ \ \ | |/ / / / / |/| | | | | Add jumplink to deleted messages
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-29 21:41:42 +0000