Mark Harrison

The bug also does not occur when running cmd.exe within [windows terminal](https://docs.microsoft.com/en-us/windows/terminal/install).

Side question. I'm confused about this: > "followable", "following", "blocking", and "followsYou" never appear in a response to a unauthenticated request. What is an authenticated request? I tried using an...

Please run lichess-bot with `-v` for verbose logging and `-l` to save the log to a file like this: `python lichess-bot.py -v -l log.txt` After a game that shows this...

Is this a stockfish issue?

This might be a relevant issue that could use some input from here: https://github.com/official-stockfish/Stockfish/issues/4000

I'm closing this bug since it doesn't seem related to lichess-bot. Please reopen if there is still a problem.

Instead of returning the comment separately, you can add it to the PlayResult.info field. See [here for reference](https://github.com/niklasf/python-chess/blob/80c718489e2bdbd597f6e2c5c02663c4c9e0265d/chess/engine.py#L381) and [here for the `__init__` argument](https://github.com/niklasf/python-chess/blob/80c718489e2bdbd597f6e2c5c02663c4c9e0265d/chess/engine.py#L403). This way, engine moves and DB...

Looks like this works. Just fix the indentation of the arguments on lines 411 to 419 of lichess-bot.py and I'll merge this.

There's an error in `get_lichess_cloud_move()` that causes the move to not be printed to the console or a logging file. Adding the line `logger.exception("lichess_cloud error:")` below `except Exception` on line...

After [this commit](https://github.com/ShailChoksi/lichess-bot/pull/574/commits/fd995fd9e773ccfe6709a6571c437e8b48e9a086), `EngineWrapper.last_move_info` is no longer used anywhere. It is written over in `EngineWrapper.search()`, but not read anywhere. Now, since `search()` calls `self.print_stats()` before the `move_commentary` is updated, it...