lorri
lorri copied to clipboard
target
Your project's nix-env
**Describe the bug** It's worth noting a few things first: - Our default.nix uses [developPackage](https://github.com/NixOS/nixpkgs/blob/9ef0636f1598a16d247cec6a4ec6893821631654/pkgs/development/haskell-modules/make-package-set.nix#L231) - Our `.envrc` calls hpack first since lorri doesn't respect shellHook as noted in #390:...
At CircuitHub, we use a single mono repo and have a `shell.nix` in it which contains, amongst other things: ```nix shellHook = '' export \ PGDATABASE=$( vault read -field=database secret/dev/staging-database...
**Feature description** I'm not sure if this is the right place to try and fix this issue with Nix, but I am curious to see other's thoughts on the mater....
I would expect that running `self-upgrade` on CI would take the lorri nix storepath we just built a step before (and thus be an instant thing), but it takes over...
https://github.com/target/lorri/blob/33cb219d8bea17dd400789eec220f0a1bdea313c/src/daemon/rpc.rs#L62 If [any varlink error](https://docs.rs/varlink/11.0.0/varlink/error/enum.ErrorKind.html) happens (that might be something permanent like a `MethodNotFound` error or something temporary, like a timeout or an IO error), the current implementation just stops...
I just noticed that lorry sets `$out`: ``` ~/foo $ echo $out /nix/store/s7zha1rssggdnvasm6mjnknrd8042kaa-lorri-wrapped-project-nix-shell ``` I noticed because I wanted to embed `$out` in a program as a source identifier when...
**Feature description** I’d like to list what the watcher is currently watching. This should make it easier to debug path problems that cause lorri to update too often. If possible,...
My apologies, but I only had time to copy paste my terminal log (though it's reproducible). Basically direnv support doesn't seem to work how I expect because it lorri doesn't...
@regnat [introduced the `--log-format` flag to nix](https://github.com/NixOS/nix/pull/3073), which makes nix print json-formatted log output. It’s not yet in a release and we are going to have to keep backwards compatibility...
**Describe the bug** Got a panic from `lorri`, apparently as a result of a chain of modifications within a single project in the course of a git rebase. **To Reproduce**...
