[ggo-discussion] Re: The FULL report about gGo claiming a game is not being played.

Uh, excuse my accidental email there.

Oh, for heaven's sake...  my last post didn't even contain the whole
message. Please disregard the last two emails. Apologies!

Anyway, I found a small bug in gGo (at least, I assume it's a problem with
gGo). These things are getting harder and harder to find, so as you can
imagine, I was quite pleased with myself. ;)
I had started a new game, and after the board had appeared, I decided to
save a game which I had finished earlier, so I went to that board and went
through the usual saving procedure. When I returned to my new game, I was
surprised to see that gGo would no let me play on the board, effectively
saying "This game is not currently being played, shall I reload it", or
something like that. Of course, I could not reload it since I was playing
it, so I had to quickly disconnect and then reconnect to IGS in order to
load the game.

Incidentally, my opponent had already played a stone (he was Black), so it
wasn't a completely fresh board, although I hadn't yet made any moves.

I've included a part of the gGo log which seems relevant:

SENDING 'match Fredrik W 19 1 5'
Remembered match time with Fredrik: [Time = 1, Stones = 25, initByoTime = 5]
Forgot match time with Fredrik
Removed match dialog: Fredrik
SENDING 'status 127'
Searching for remembered time settings for: Fredrik
gameID = 127, newOwnGameID = 127
Did not find a board to reuse, opening new.
BoardHandler.addMoveIGS(): lastValidMove is null
recieveMoveFromHuman(): I don't play game 127
IGSPlayingFrame.recieveMoveFromHuman() failed for game ID 127
Reloading game on user request.
SENDING 'load Moridin-Fredrik'
recieveMoveFromHuman(): I don't play game 127
IGSPlayingFrame.recieveMoveFromHuman() failed for game ID 127
SENDING 'stats'
recieveMoveFromHuman(): I don't play game 127
IGSPlayingFrame.recieveMoveFromHuman() failed for game ID 127
...

...whereupon I decided to disconnect from IGS

Other related posts: