Closed GoogleCodeExporter closed 9 years ago
in RC9 I just observed a bughouse game that ended in time forfeit and I got the
red *. It also says "Interrupted by unobserve" below the boards. What I think
is actually happening is that Raptor is perceiving the wrong order of FICS
messages because in the console it says this:
12:01AM
Removing game 259 from observation list.
12:01AM
Removing game 213 from observation list.
12:01AM {Game 213 (EEKarf vs. Liverppol) EEKarf's partner won} 1-0
12:01AM {Game 259 (smotherhubbard vs. IndianReaper) smotherhubbard forfeits on
time} 0-1
Original comment by jessego...@gmail.com
on 28 Feb 2011 at 5:17
I think that delay i removed to speed up timeseal was preventing this before. I
will take a close look at how the messaging works next weekend.
Original comment by carsonday
on 28 Feb 2011 at 5:19
Come to think of it, when I "tell babaschess stats" I get a screwy order or
Qtells back as well:
12:17AM tell babaschess stats
12:17AM (told BabasChess)
12:17AM :Statistics over 27372 registered user logins recorded in the last 30
days (in case of more logins of the same user, only the last one is considered)
12:17AM :Jin Applet: 5542 (20.25%)
12:17AM :BabasChess: 12306 (44.96%)
12:17AM :Jin: 2381 (8.70%)
12:17AM :WinBoard: 1707 (6.24%)
12:17AM :Odesys Chess: 1294 (4.73%)
12:17AM :Unspecified: 852 (3.11%)
12:17AM :Thief: 797 (2.91%)
12:17AM :Other: 757 (2.77%)
12:17AM :EBoard: 628 (2.29%)
12:17AM :XBoard: 279 (1.02%)
12:17AM :CClient: 239 (0.87%)
12:17AM :iNemesis: 147 (0.54%)
12:17AM :Slics: 33 (0.12%)
12:17AM :CheckMate: 27 (0.10%)
12:17AM :Decaf: 17 (0.06%)
12:17AM :Pocket PC ThinkerBoard: 17 (0.06%)
12:17AM :Arena: 86 (0.31%)
12:17AM :Raptor: 166 (0.61%)
12:17AM :Chess Machine: 11 (0.04%)
12:17AM :LightningRulez: 9 (0.03%)
12:17AM :ChessPartner: 6 (0.02%)
12:17AM :ChessBD: 4 (0.01%)
12:17AM :Knights: 2 (0.01%)
12:17AM :Thanx: 2 (0.01%)
12:17AM :JavaBoard: 0 (0.00%)
12:17AM :Fixation: 63 (0.23%)
12:17AM :Freak: 0 (0.00%)
12:17AM :Varese: 0 (0.00%)
This doesn't look too good. :(
Original comment by jessego...@gmail.com
on 28 Feb 2011 at 5:20
QTells:
Its because each line is treated like a new message (the way fics sends them)
and they are dispatched asynchronously to the chat console.
Red *:
Were you getting this when doing follow /B?
Original comment by carsonday
on 2 Mar 2011 at 12:20
This issue was closed by revision r2078.
Original comment by carsonday
on 2 Mar 2011 at 1:06
actually obs /B
Original comment by jessego...@gmail.com
on 2 Mar 2011 at 1:14
This is still an issue.
Original comment by carsonday
on 2 Mar 2011 at 3:36
Original comment by carsonday
on 5 Mar 2011 at 10:22
Original comment by carsonday
on 6 Mar 2011 at 4:23
Original issue reported on code.google.com by
jessego...@gmail.com
on 28 Feb 2011 at 3:32