Profpatsch
Profpatsch
> For nix-based builds, part of the puzzle is of course that we've disabled cachix on macOS due to this issue: [cachix/cachix#228 (comment)](https://github.com/cachix/cachix/issues/228#issuecomment-533634704). That’s fixed since #340 Build times seem...
The caching for the macos nix build still has some problems: https://travis-ci.org/target/lorri/jobs/657713960?utm_medium=notification&utm_source=github_status
Is there anything to do from our side? I don’t think we can influence this much, and people are going to open issues when they have problems anyway.
Did the merged PR lead to fixing this issue?
@curiousleo did the merged PR fix this issue?
`lorri shell` does set it iirc. There was a reason why we don’t set it which should be documented somewhere in the code or git blame.
Looks like we are setting it in two places: https://github.com/nix-community/lorri/blob/dfbf9b3d22474380ee5e096931dbf25b1c162d10/src/ops/direnv/envrc.bash#L163 https://github.com/nix-community/lorri/blob/b84602c7132293e23eb8957ba493f188ce89ea1c/src/logged-evaluation.nix#L144
yeah, with `type lorri >/dev/null` I guess
Hi @maxdevjs, could you please run the following commands: ```console $ lorri info $ uname -a ```
Ah, the rust stdlib thing where they don’t give you the file that it tried to access. Can you strace it to see which file it tried to access?