On Tue, Oct 06, 2009 at 05:13:17PM +0100, Nick Wedd wrote:
> In message <wladvtgcx1ykf...@maproom.demon.co.uk>, Nick Wedd
> <n...@maproom.co.uk> writes
> >Congratulations to AyaMC, winner of Sunday's KGS Computer Go
> >tournament! My report is at
> >http://www.weddslist.com/kgs/past/52/index.html
> >
> >Two people had bots crash after receiving the message
> >"FINEST: Still an outstanding command". I do not know what this
> >means, and am reporting it to wms.
>
> I have heard back from wms:
>
> > The "still an outstanding command" message means that a
> > command has been sent to the engine, but the engine hasn't yet
> > answered it. That's probably a bug in the engine, because GTP
> > requires all commands to be answered with an acknowledgement
> > or an error.
>
> So it seems that CzechBot (=MoGo) and Fuego need to implement
> something, I don't know what. It's strange that this has never come
> up before.
This is caused by the fact that both CzechBot and Fuego (probably) were
stuck up in reading, probably either getting dead-locked or stuck in
some infinite loop; so in fact the outstanding command was genmove, and
neither of these ever chose which move to play. CzechBot wasn't even
printing out any progress lines.
I think the problem here is that when kgsGtp reconnects, it does not
restart the engine; I think doing that would help a lot in these
situations, since a stuck engine would be restarted by the reconnect.
Right now, after reconnecting, kgsGtp was still waiting for the original
genmove command from "old" connection to finish.
--
Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
