| Commit message (Collapse) | Author | Lines |
|
python-discord/.github
|
|
Please have a bit of respect to the baguette land. Also this is a good way to test the new deploy approval system.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bug caused by an outdated function signature in a previous commit in the #1402 PR
|
|
|
|
|
|
Co-authored-by: Boris Muratov <[email protected]>
|
|
|
|
Co-authored-by: Boris Muratov <[email protected]>
|
|
|
|
|
|
- Add disable_header to watchchannel initialization.
We don't have root actor field anymore, so headers give error
and there is no point to rewrite this, because this will be
removed soon.
- Removed duplicates check of nominations of one user.
Now as API allows this, multiple actors can nomination one
user.
- Add special error message if same actor have already nominated user
Every actor can only have 1 nomination entry.
- Remove previous reason from watch command
We don't store reason that way anymore, and we don't want
that this message spam whole channel.
- Split end reason and reason editing commands.
API PATCH request buildup have been changed, so changing both
of them in one command don't make sense anymore.
- Migrate nomination string generation
|
|
We need to disable this, because new format of nominations
don't match with it.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|