Improve / Extend ready signalling with `Juptyerlite` kernel

[stevejpurves]

Context

thebe's usual bootstrap sequence of connecting to a server and starting a session works well with binder and Jupyter server connections, where a session "ready" status can be shown reliably when the kernel is started and ready for code to be executed.

When attaching to a JuptyerLite kernel however, the "ready" status comes back early, whilst the server / session is still being setup. I think this is because the kernel is active but executing piplite commands to load packages.

At the moment thebe is not able to get any progress information on that process, to cannot wait on it to complete, or handle errors that arise during that process.

Proposal

Investigate?

• Is there a way to improve this and get something to wait on or a stream that can be monitored for progress in some way?
• Is a different piplite module loading strategy that can be used to improve this experience?

Tasks and updates

No response

[stevejpurves]

Solution for this is in an upstream PR https://github.com/jupyterlite/jupyterlite/pull/900

[jtpio]

FYI a new release of JupyterLite is out with the fixes from https://github.com/jupyterlite/jupyterlite/pull/900: https://github.com/jupyterlite/jupyterlite/releases/tag/v0.1.0b17