Open GoogleCodeExporter opened 9 years ago
I have been able to reproduce this issue by doing: "seek 60 5 odds
queen-and-move black manual f" just like QBall did in the example and then
viewing the seek with "sought all". My guess is that the dashes in
"queen-and-move" crash the connection because "seek 60 5 odds rook-and-move
black manual f" will cause the same problem.
Because this not only throws an error but kills the connection to FICS I will
change this to Medium priority.
Looking further into this problem I find that when Raptor displays a sought
list in the console and there happens to be a line with brackets such as (C)
Raptor will think that this line is a news item and double clicking on it will
attempt to open the news item with the beginning number's index.
You can notice through experimenting that Raptor always changes the rating
range to "0- 0" if the seek was issued by a registered user with a rating of
"----", but Raptor will keep the actual rating range if the seek was issued by
a guest with a rating of "++++"
There are 22 board types that contain dashes and I assume they all kill
Raptor's connection to FICS when viewed with the sought command:
misc/queen-power
misc/no-castle
misc/knight-power
misc/no-queens
misc/bishops-only
misc/rook-power
misc/rooks-only
misc/knights-only
misc/minor-power
misc/bishop-power
misc/queens-only
misc/queen-rooks
misc/full-power
odds/knight-and-move
odds/pawn-and-move
odds/queen-and-move
odds/rook-and-move
odds/bishop-and-move
pawns/little-game
pawns/pawns-only
pawns/wild-five
pawns/pawn-power
This bug is an interesting and important one and I'd love to try and figure it
out but I know nothing of Raptor's parsing code other than it is probably
really complicated. While this specific bug is important, there will *always*
be FICS messages that Raptor has trouble understanding. How do all the other
interfaces deal with the extremely rare cases that should put the interface
into a panic?
Original comment by jessego...@gmail.com
on 3 Feb 2013 at 11:28
Pretty easy to reproduce this bug on unbuntu using Raptor .99f1. Happens
every time.
Original comment by mdrmike...@gmail.com
on 15 May 2014 at 12:53
Original issue reported on code.google.com by
skqui...@gmail.com
on 10 Aug 2012 at 6:23