Re: [computer-go] Slight glitch on 'undo' as handled by kgsgtp

[<john@xxxxxxxxxxxxx>]

Thanks for fixing them!

And all the rest of the hard work to get KGS where it is; is there an
address to send beer vouchers?
John


> Well, I can always tell when new clients start using kgsGtp because
> they find new bugs! There were two found in the past few days:
>      * Returning an error to the "final_status_list" command hangs the
>        client, found by Lukasz Lew and reported in an earlier email
>      * The bug listed below: when you support "clear_board" but not
>        "undo", and play as black in a 9x9 handicap game with free
>        placement, you don't get the handicap stones sent to you after
>        your opponent makes an undo.
> Both will be fixed in the 2.6.10 release. Thanks!
>
> On Sat, 2005-03-19 at 20:51 +0000, john@xxxxxxxxxxxxxxxxx wrote:
>> Just a quick bug report (mainly to wms, but others may have hit this
>> and wondered what went wrong).
>> I don't handle "undo" requests in Dumbbot yet.  As I don't advertise
>> this in "list_commands", the kgsgtp wrapper does it for me every time
>> a human loser hits undo during a Free game (2 or 3 times a game isn't
>> rare - it's surprising DB ever gets to win!)  It does this by sending
>> a boardsize command which clears everything down, resends komi,
>> time_settings etc and then sends "play" commands to repopulate the
>> board as it was just prior to the "undo" move.  All very clever and
>> seems to work fine.
>> However - if the game is a handicap one, the wrapper fails to resend
>> the "place_free_handicap n" command after the "boardsize" command
>> clears the game.  This leaves the server out of sync with the engine
>> which eventually comes up with an illegal move; this illegal move
>> causes kgsgtp to dump the engine in disgust ;-)
>> It took me a while to track this one down.  I presumed it was another
>> one of the many daft mistakes I've made in DB so far.  I've got all
>> the logfile output if needed, but I'm guessing it was one of those
>> unthought-of combinations that slipped through and won't take long to
>> fix. Maybe DB is the only Bot that doesn't honour the "undo" command?
>>
>> HTH
>>
>> John
>>
>>
>> _______________________________________________
>> computer-go mailing list
>> computer-go@xxxxxxxxxxxxxxxxx
>> http://www.computer-go.org/mailman/listinfo/computer-go/
>>
>
> _______________________________________________
> computer-go mailing list
> computer-go@xxxxxxxxxxxxxxxxx
> http://www.computer-go.org/mailman/listinfo/computer-go/



_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/