Closed benckx closed 4 months ago
We now ensure incorrect engine data is not persisted, and the existing data has been cleaned up. But it's not clear how it happens. Probably something in the Analysis Board JS code, which has to do with concurrency.
In this analysis on move 6 the PV line is the same for both half moves, which doesn't make sense (board crashes when clicking on first move of PV line). It means the FEN key is mapped to an incorrect engine info line result. https://elephantchess.io/analysis?id=hsERAZo09R4g
As a first workaround, the Analysis Board could remove/refuse entries with incorrect PV line, so it would be recalculated.