🪐 JupyterLab: Kernel

Question

🪐 JupyterLab: Kernel

Opened this issue 2 months ago · 5 comments

Note

I ❤ writing tickets in the place where our work is managed.

User feedback from User Research into JupyterLab.

"Using existing home directory
Existing kernels don’t work
Kernels in $HOME/.local/share/jupyter/kernels point to locations starting /home/joyvan rather than /home/analyticalplatform"

Examine this in detail to understand any implications.

Answer 1 · 2024-11-07T16:58:36.000Z

Having discussed this with @jacobwoffenden - our approach will be to add a new init file in src/opt/analytical-platform/init in the base image. In this file we can search for all kernel.json files in users home/joyvan directories and sed for joyvan to replace it with analyticalplatform.

Answer 2 · 2024-11-12T13:43:24.000Z

Currently investigating random users kernels in the aforementioned location.

Answer 3 · 2024-11-14T16:49:24.000Z

Wrote a script to enable us to examine the deployed image versions of all tools for all users as part of this piece of work. Output is in a thread in main channel.

Setup another script which I'm testing locally at the moment to perform the desired function of this piece of work.

Answer 4 · 2024-11-14T17:57:32.000Z

🚧 WIP PR here. Pivoting this to be added into the Jupyter image rather than the CBDE image.

Thinking this through further, the implications of this script as it is currently described will have effects on the images which users are currently consuming. i.e. altering kernel.json will mean we will edit files that are called in the images users are currently consuming 🤔

Answer 5 · 2024-11-18T16:42:42.000Z

Initial thinking on the above issue has changed slightly.

By copying files from /home/joyvan to /home/analyticalplatform and editing the newly created kernel.json files to reference analyticalplatform we can ensure that even if the script does run, users will still be able to consume older images in the beta period.