Nantes Université

Skip to content

Update environements list on the submission form when an environnement is added or removed

Based on @hervy-b report, it seems that when a new jupyter environnement is created by a user (with the correct ipykernel dependency and kernel [*]), the environnement is not properly added to the jupyter environnements available for this user (despite refresh and logout/login attempts):

image

vs expected:

image

At the moment it is unclear where the environnements list is cached by the system (this should also apply to the available ressources allocation but it seems to work fine on this front…).

[*] Adding a new jupyter environnement to the jupyter submission form is currently not properly documented:

micromamba activate <ENV>
micromamba install ipykernel
python -m ipykernel install --display-name="Python (<ENV>)" --prefix=/micromamba/<USERNAME>/envs/<ENV>

Workaround

It seems that rebooting the hub refresh the interface and solve the issue. This is not how it should be handle and addition/removal of environnement should be apply to the user submission form upon refresh of the form.

To do

  • For a logged-in user, create a new jupyter environnement, refresh the form to see if the environnement was correctly added to environnements list.
  • The same behavior is expected on team and global environnements.
  • The same behavior is expected when a jupyter envs is removed.
Pour téléverser des designs, il est nécessaire d'activer LFS et que l'administrateur ait activé le stockage haché. En savoir plus