Profpatsch

We cannot run `shellHooks` outside of a nix build environment, because of the effects described in https://github.com/target/lorri/issues/7#issuecomment-480298131. What we *could* do though, is introduce a special field, e.g. `lorriHook`, which...

Unfortunately your lorri version does not have the change that improved error message, so I can only guess where the io error was thrown originally. :( We propagate errors out...

what is your nix version? This looks like a bug that existed in an older nix version (the `.drv` file is parsed as if it were a `.nix` file)

you might be running into this issue: https://github.com/target/lorri/issues/159 Can you update to nix 2.3.2?

You would have to use the `lorri internal stream_events` command (huh, where do the underscores come from) and combine it with a service manager that you run your project’s services...

@nodew what happens if you run ``` nix-build /nix/store/lf7dqzyc68qm4d8q98dkilci7gfzzn2i-wrapped-project-nix-shell.drv ``` and what happens if you run ``` nix-store --realise /nix/store/lf7dqzyc68qm4d8q98dkilci7gfzzn2i-wrapped-project-nix-shell.drv ``` instead?

Interesting, so the bug in `nix-build` is still not fixed. I thought it was. whoa, we had this on macOS a while ago: https://github.com/target/lorri/issues/179 But since you are on NixOS...

To be clear here, this is a bug we can fix by using `nix-store` instead of `nix-build` internally, but because the original bug report in #179 seemed to have gone...

I created an issue with a description of what needs to be done in order to fix this: https://github.com/target/lorri/issues/362

I’m using the `s6` approach in a production project and it’s working quite nicely (though I don’t have any automatic restart set up, I just do it manually when necessary).