A bug in the conditional move interface was responsible for the unexpected mates.
This has now been fixed - some very good descriptions of how the bug occurred by 2 people really helped get to the bottom of this. So thanks for that.
For those who are interested, the bug involved placing yourself in mate, then trying to submit a move out of it on the conditional move interface. This resulted in a short-circuit in the RHP code declaring the game as over based on the current state of the conditional board.
It was a rare bug, but we can sleep easier now knowing it has been squished.
Originally posted by Russ A bug in the conditional move interface was responsible for the unexpected mates.
This has now been fixed - some very good descriptions of how the bug occurred by 2 people really helped get to the bottom of this. So thanks for that.
For those who are interested, the bug involved placing yourself in mate, then trying to submit a move out of it on the cond ...[text shortened]... tional board.
It was a rare bug, but we can sleep easier now knowing it has been squished.
Originally posted by Russ A bug in the conditional move interface was responsible for the unexpected mates.
This has now been fixed - some very good descriptions of how the bug occurred by 2 people really helped get to the bottom of this. So thanks for that.
For those who are interested, the bug involved placing yourself in mate, then trying to submit a move out of it on the cond ...[text shortened]... tional board.
It was a rare bug, but we can sleep easier now knowing it has been squished.
Ah, that explains a lot. When you said that the bug was connected to the conditional moves I was sceptical as I was 99% sure I never submitted any. I never considered that it was my opponent who made the conditional move sequence. Good work.
Originally posted by peacedog Ah, that explains a lot. When you said that the bug was connected to the conditional moves I was sceptical as I was 99% sure I never submitted any. I never considered that it was my opponent who made the conditional move sequence. Good work.
The lack of recorded conditional moves against games that had this problem almost made us rule it out, but the timing of the first occurrence was around the time of the non-beta release of conditional moves. So, there had to be a connection somewhere...
Can't take the credit for this one really, fixing the bug was straight forward once the issue could be replicated, and Chris was on a mission to find the cause which lead to the discovery of the problem once he messaged players reporting the problem.