You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.
I have a bot that's logging all games on the server for analysis. In some cases where White plays a move and then the game ends (I can't tell from logs if this is due to time or resignation or what), it double-sends the opening move.
2016/05/04 10:46:26 < GameList Add Game#309 TakticianBot vs onewhohides, 5x5, 1200, 0 half-moves played, TakticianBot to move
2016/05/04 10:46:26 > Observe 309
2016/05/04 10:46:26 < Observe Game#309 TakticianBot vs onewhohides, 5x5, 1200, 1 half-moves played, onewhohides to move
2016/05/04 10:46:26 < Game#309 P A1
2016/05/04 10:46:26 < Game#309 Time 1200 -2216321
2016/05/04 10:46:26 < Game#309 P A1
2016/05/04 10:46:26 < Game#309 Time 1200 -2216321
2016/05/04 10:46:26 < GameList Remove Game#309 TakticianBot vs onewhohides, 5x5, 1200, 1 half-moves played, onewhohides to move
2016/05/04 10:46:26 < Game#309 Over 1-0
2016/05/04 10:46:26 < GameList Remove Game#309 TakticianBot vs onewhohides, 5x5, 1200, 1 half-moves played, onewhohides to move
There's also some weirdness with the time, which is being reported as -2216321 here…
The text was updated successfully, but these errors were encountered:
This looks like a synchronization issue. Currently, when I add a new spectator, I send the move list, but if the one of the players moves at the same time, there is a possibility of sending the move twice.
Thanks for the bug report, I'd not noticed it before.
I have a bot that's logging all games on the server for analysis. In some cases where White plays a move and then the game ends (I can't tell from logs if this is due to time or resignation or what), it double-sends the opening move.
There's also some weirdness with the time, which is being reported as
-2216321
here…The text was updated successfully, but these errors were encountered: