Update lite build in documentation

[martinRenou]

• Switch to using jupyterlite-xeus
• Install dev version of jupyterlab-blocky in documentation Does not work actually

[github-actions]

👈 Launch a Binder on branch martinRenou/jupyterlab-blockly/update_lite_build

[martinRenou]

This seems to be working now:

I see two issues though:

• the blockly UI is not in english?
• the kernel UI does not show up

[DenisaCG]

Thank you for working on this @martinRenou!

I'm not sure what the issue with the language or the UI is, but it might be coming from the version of the blockly library we are using. I will look into it.

[martinRenou]

Thanks!

[DenisaCG]

the blockly UI is not in english?

Did you use the development install aspip install -e . ".[dev]"?
And was your JupyterLab originally set in English? Did you have other language packages installed? @martinRenou

[martinRenou]

Sorry I did not clarify, the screenshot was taken from the readthedocs deployment for this PR:

https://jupyterlab-blockly--83.org.readthedocs.build/en/83

This build uses the environment https://github.com/QuantStack/jupyterlab-blockly/pull/83/files#diff-4c1832e89e371aa749c45d5942a4b294b068f05c43e1ffc2e16457331c3d020eR1

[DenisaCG]

After some debugging, the error with the JupyterLite deployment of jupyterlab-blockly seems to come from the version of JupyterLab it's using, as the function from the kernel UI seems to have changed in the later versions. In our extension we currently set up the kernel commands like this:

jupyterlab-blockly/packages/blockly-extension/src/index.ts

Lines 217 to 243 in de7fbb8

	if (mainMenu) {
	mainMenu.kernelMenu.kernelUsers.add({
	tracker,
	interruptKernel: current => {
	const kernel = current.context.sessionContext.session?.kernel;
	if (kernel) {
	return kernel.interrupt();
	}
	return Promise.resolve(void 0);
	},
	reconnectToKernel: current => {
	const kernel = current.context.sessionContext.session?.kernel;
	if (kernel) {
	return kernel.reconnect();
	}
	return Promise.resolve(void 0);
	},
	restartKernel: current => {
	const kernel = current.context.sessionContext.session?.kernel;
	if (kernel) {
	return kernel.restart();
	}
	return Promise.resolve(void 0);
	},
	shutdownKernel: current => current.context.sessionContext.shutdown()
	} as IKernelMenu.IKernelUser<BlocklyEditor>);
	}

but in JupyterLab since v4.0.0 they are set up like this:

https://github.com/jupyterlab/jupyterlab/blob/bb8a4edbe6fdfcd8abb763b414adf37e84aa2f08/packages/console-extension/src/index.ts#L836-L856

As a temporary fix, so the JupyterLite deployment works, we can pin the version of JupyterLab to be the latest compatible one, which would mean adding the following lines to docs/build-enviroment.yml:

- python=3.9
- jupyterlab=3.6.7

I have tried this locally and it should fix the kernel UI error.

Is there another way you recommend we deal with this for now?

In any case, I think migrating jupyterlab-blockly to v4 of JupyterLab should be done soon and would be the best solution in the long run :)

[martinRenou]

Thanks for investigating this!

Unfortunately using the latest jupyterlite we're stuck with jupyterlab v4, so we need to downgrade jupyterlite for now. Let's see if that works.

[martinRenou]

We need a release of jupyterlite-xeus with jupyterlite/xeus#73 and I believe we should be good to go

[martinRenou]

It's working again! https://jupyterlab-blockly--83.org.readthedocs.build/en/83

[martinRenou]

@DenisaCG let's get this merged and we can fix the check-release workflow separately

[DenisaCG]

Great, thanks Martin!