lichess-bot sending quit to UCI on startup

[staceycampbell]

I'm trying to set up lichess-bot to use my UCI engine. The basic UCI startup comms appear to be working, but lichess-bot sends a quit, then about a minute later exits with an extensive debug log.

I believe I've executed all the steps as outlined in the doc up until this failure.

I've attached the log.txt.

Sorry, I'm not familiar with python so I'm not sure how to proceed.

The engine has played a few thousand games on FICS using UCI, polyglot, and xboard, so conceptually I believe it can work.

Thanks,

Stacey

[MarkZH]

Judging by the last two lines before the traceback:

2026-03-16 16:49:31,646 chess.engine (engine.py:950) DEBUG <UciProtocol (pid=3241502)>: << quit
2026-03-16 16:50:31,664 lib.lichess_bot (lichess_bot.py:1278) ERROR Quitting lichess-bot due to an error:

a full minute passed after your bot received the quit command and lichess-bot shutting down due to a timeout.

At this point in the lichess-bot run, the bot is started and shutdown immediately as a check that the bot is minimally functional and communicative with lichess-bot.

As a check, start your bot manually on the command line and manually type uci, isready, and quit. Check if your bot successfully quit.

I took a quick look at your code, and it doesn't seem like the quit command is handled in uci_dispatch() in src/uci.c.

[staceycampbell]

Thanks for the explanation, that was the problem.

I was incorrectly dealing with quit in vivado/comms/numbattcp.c, that's the bridge between the ARM inside the FPGA and the outside world.