- Blind mode tutorial
lichess.org
Donate

Chessboard doesn't set only a specific premove

#1

I found this strange behaviour that feels like a bug

https://lichess.org/31Gg9WdO/black#43

In the 9th move just after castling I try to set pawn in f7 to prawn e6 recapture as a premove.
I can't, f7 pawn is the only piece that can't accept premove.
I tried many times in many subsequent moves, I can still set premoves on other piece (so definitely I was connected and not a lag issue) but f7 don't accept premoves and if I click on it in other player turn it behaves like I am trying to move it (and don't allow me to do so)

Again not a lag issues, chessboard was responsive the whole time, simply clicking on f7 behave differently.
I got curious and in the subsequent moves like 12th and 13th I have tried to set/reset many premoves, alternating f7 to others; f7 is the only one that doesn't set.
Other pieces (pawn included) works as intended.

So I see from game times analysis that while I was testing the opponent didn't move (so I should premove any piece).
The fact that indeed other pieces allow to premoves and set premoves corroborate that.
The fact that systematically (in many occasions) it's only f7 that doesn't set/reset while I was trying let me think that a disconnection was not plausible because should be intermittent and happening systematically only while I test f7 (highly unlikely, almost impossible).
In any case while I was playing the connect was great in general and also in Lichess I didn't see anything strange.

Ps: while I write that I test premoves set/reset interleaving f7 test, I mean that while my opponent take ~10s to make 12th moves I try to :
-set a7 to a6 or a5 premove, seen that premove was correctly setted (gray square appear)
-click another piece to reset all premoves (correct, no premoves remain)
-try to set f7 to e6 and see that clicking on f7 try to move the pawn like it was my turn (failure no premoves was setted).

  • restart testing (with success) a7

I do ~3 loop and the give up.
So the probability that a good internet connection (and a good indicator also in Lichess) doesn't show an intermittent connection issues that happens only and last only while I test f7 is almost 0

All the tests was made on Android device with chrome.

I found this strange behaviour that feels like a bug https://lichess.org/31Gg9WdO/black#43 In the 9th move just after castling I try to set pawn in f7 to prawn e6 recapture as a premove. I can't, f7 pawn is the only piece that can't accept premove. I tried many times in many subsequent moves, I can still set premoves on other piece (so definitely I was connected and not a lag issue) but f7 don't accept premoves and if I click on it in other player turn it behaves like I am trying to move it (and don't allow me to do so) Again not a lag issues, chessboard was responsive the whole time, simply clicking on f7 behave differently. I got curious and in the subsequent moves like 12th and 13th I have tried to set/reset many premoves, alternating f7 to others; f7 is the only one that doesn't set. Other pieces (pawn included) works as intended. So I see from game times analysis that while I was testing the opponent didn't move (so I should premove any piece). The fact that indeed other pieces allow to premoves and set premoves corroborate that. The fact that systematically (in many occasions) it's only f7 that doesn't set/reset while I was trying let me think that a disconnection was not plausible because should be intermittent and happening systematically only while I test f7 (highly unlikely, almost impossible). In any case while I was playing the connect was great in general and also in Lichess I didn't see anything strange. Ps: while I write that I test premoves set/reset interleaving f7 test, I mean that while my opponent take ~10s to make 12th moves I try to : -set a7 to a6 or a5 premove, seen that premove was correctly setted (gray square appear) -click another piece to reset all premoves (correct, no premoves remain) -try to set f7 to e6 and see that clicking on f7 try to move the pawn like it was my turn (failure no premoves was setted). - restart testing (with success) a7 I do ~3 loop and the give up. So the probability that a good internet connection (and a good indicator also in Lichess) doesn't show an intermittent connection issues that happens only and last only while I test f7 is almost 0 All the tests was made on Android device with chrome.
#2
<Comment deleted by user>
#4

@TBest said in #3:

Can you reproduce it? (

I can't.

The only recent relevant change I am aware of is github.com/lichess-org/chessground/pull/336

What described in the PR (from my interpretation) seems vaguely related to my situation (a specific menaced pawn in first rank that doesn't works correctly in a premove).
So maybe a side effects of the change?

Any suggestions on how many I try to reproduce it? I will try but not sure what to do (I think I need a match that redo moves)

@TBest said in #3: > Can you reproduce it? ( > > I can't. > > The only recent relevant change I am aware of is github.com/lichess-org/chessground/pull/336 What described in the PR (from my interpretation) seems vaguely related to my situation (a specific menaced pawn in first rank that doesn't works correctly in a premove). So maybe a side effects of the change? Any suggestions on how many I try to reproduce it? I will try but not sure what to do (I think I need a match that redo moves)
#5

https://lichess.org/KJDpBq1rEFaB

Reproduced by accident here.
Starting see a scheme.
If the third pawn from the left try to set a pre move of recapture on the fourth advanced pawn from the left, the premove is not set.

I still don't know if it's a consistent issues I will update soon

----------Edited
Yep a consistent issue let me know if now also you were able to reproduce the issue

https://lichess.org/Q7acvmMSxVuf

https://lichess.org/KJDpBq1rEFaB Reproduced by accident here. Starting see a scheme. If the third pawn from the left try to set a pre move of recapture on the fourth advanced pawn from the left, the premove is not set. I still don't know if it's a consistent issues I will update soon ----------Edited Yep a consistent issue let me know if now also you were able to reproduce the issue https://lichess.org/Q7acvmMSxVuf
#6

@Lichess any plan to fix the bug.
More I play and more the chessboard feel clunky lately.

After further investigation and testing seems that premoves for recapture didn't work if pawn is on the first rank regardless of everything else.

Tested on chrome mobile with Android

@Lichess any plan to fix the bug. More I play and more the chessboard feel clunky lately. After further investigation and testing seems that premoves for recapture didn't work if pawn is on the first rank regardless of everything else. Tested on chrome mobile with Android
#7

If you want something fixed make a github issue https://github.com/lichess-org/lila/issues

I either can't reproduce it or I don't understand what you mean. So probably best if you create an issue and fill out steps to reproduce it.

If you want something fixed make a github issue https://github.com/lichess-org/lila/issues I either can't reproduce it or I don't understand what you mean. So probably best if you create an issue and fill out steps to reproduce it.
#8

I would like report that this morning the issue erratically happen again.

Sometimes there are specific legal premoves that I can't make while I waiting.
Very often happens that is the recapture from a pawn that is still on the first line.

I tried to clean cache last time and after the many updates the issue disappeared.. but now happens again, with the difference that is not systematic

I would like report that this morning the issue erratically happen again. Sometimes there are specific legal premoves that I can't make while I waiting. Very often happens that is the recapture from a pawn that is still on the first line. I tried to clean cache last time and after the many updates the issue disappeared.. but now happens again, with the difference that is not systematic

This topic has been archived and can no longer be replied to.