Bot loses lock occasionally about discordwordlebot HOT 2 OPEN

Preceding successful commands in channel:

%s 10 puzzle
%h

Bombed on:

%g overfishes

(Issued ~3 min after last successful command in channel)

from discordwordlebot.

I have found an issue with the lock implementation that will ultimately need to be resolved, however I do not believe that is what is actually behind this particular bug. I've been able to simulate the error message locally simply by adding an async sleep call of 5 seconds in the Wordle.guess function, however in that simulation the bot will still process incoming commands after raising the exception.

My theory right now is that something is hanging and erroring in the ctx.send call, possibly from rate limiting or some kind of connection error. Because of how the lock is implemented as a context manager, if ctx.send throws an exception after the lock has reached its timeout, the HTTP exception will get swallowed.

PR #16 adds a switch to apply the log_level setting globally. Once merged:

• set log_level to debug and verbose to true, restart the bot, and wait for the issue to emerge.

When it happens again, and before restarting:

1. check if the game lock exists in redis. The following will output all existing redis keys, which should suffice.

# assuming redis is listening on 127.0.0.1:6379

$ redis-cli -h 127.0.0.1
127.0.0.1:6379> keys *
1) "wordle:server:<server_id>:channel:<channel_id>:game"
2) "wordle:server:<server_id>:channel:<channel_id>:lock"

2. grab logs
3. wait at least a few minutes and then try entering some other commands prior to restarting

from discordwordlebot.