Matthew Kenigsberg
Matthew Kenigsberg
That was fast :) Thanks!
> Just FYI, even though I can build `main` locally, my `nix-darwin` upgrade failed: > > ``` > > src/realisepkgs/realise.cc:60:9: error: no member named 'force' in 'nix::eval_cache::CachedEvalError' > > e.force();...
Confirmed we have the fix with 1.3.4 in `/usr/local/share/fish/vendor_completions.d/flox.fish`
Submitted a PR to respect `JUPYTER_PATH` in nixpkgs
@zmitchell do you have a branch with WIP or something? I couldn't find a PR
- Need to figure out runtime local history
> * Need to figure out runtime local history We might be able to use `task_local`?
Seemed to work for me with 8 `concurrent_async_` tests and `#[tokio::test(flavor = "multi_thread", worker_threads = 4)]`. Were you seeing it fail somehow when not using a single-threaded runtime?
Don't forget to handle the case where there's a socket but process-compose isn't running
> Upon learning of the existence of `flox activate --mode run`, I intuitively ran `flox help activate` and it did work 🥳 I do notice, however, that `flox help` is...