Explicitly depend on env for Jupyter tasks

This way the Jupyter environment is built during home instantiation and
not only when actually calling the launcher script. This solves various
GC and network availability related issues for this task type.

1 files changed, 2 insertions, 2 deletions

diff --git a/tasks/default.nix b/tasks/default.nix
index 124f1cc..b3c0a1a 100644
--- a/tasks/default.nix
+++ b/tasks/default.nix
@@ -32,9 +32,9 @@ let
     rev = "7a6716f0c0a5538691a2f71a9f12b066bce7d55c";
   }) {};
 
-  mkJupyterEnv = kernel: (jupyter.jupyterlabWith {
+  mkJupyterEnv = kernel: jupyter.jupyterlabWith {
     kernels = [ kernel ];
-  }).env;
+  };
 
 in {
   custom.tasks = {