jupyenv JupyterLab IHaskell cell execution number

Because jupyenv is on JupyterLab v3.5.0, it is effected by this bug. https://github.com/jupyterlab/jupyterlab/issues/13383

The last JupyterLab version which did not have this bug was JupyterLab v3.2.4.

Is there a way to select the JupyterLab version in jupyenv?

Feb 22 '23 05:02 jamesdbrock

You could try the LSP PR with the option of https://github.com/tweag/jupyenv/pull/426/files#diff-24cbae53da3e4c7b899685295737b955daa048345f53ef85ab51b07270d7b31eR141

Feb 22 '23 22:02 GTrunSec

does not change to cell execution number

@jamesdbrock I have updated the jupyterlab to 3.6.x, that issue will not appear after restarting the kernel.

Mar 06 '23 01:03 GTrunSec

I just checked and this bug is still present in jupyenv’s JupyterLab v3.6.1. But it’s fine with me if you want to close this issue. This is not a jupyenv problem, it’s a JupyterLab problem.

Mar 09 '23 00:03 jamesdbrock

I just checked and this bug is still present in jupyenv’s JupyterLab v3.6.1. But it’s fine with me

@jamesdbrock This problem will not occur again when you run restart kernel for the second time, could you check that?

Mar 09 '23 01:03 GTrunSec

I have marked @jamesdbrock issue. Once #450 is resolved, I will provide an interface to downgrade/upragde the jupyterlab. Also, I believe that the codedown.desktop would be the best frontend for the haskell-kernel project(most importantly, it provides the hls support).

Mar 09 '23 01:03 GTrunSec

@jamesdbrock This problem will not occur again when you run restart kernel for the second time, could you check that?

When I restart the kernel over and over again, I find that the bug appears about 80% of the time after each kernel restart.

Mar 09 '23 01:03 jamesdbrock