John Eikenberry
John Eikenberry
> Though I doubt you will be able to repro it as it started happening after a period of time and a lot of activity. FYI this isn't the case....
I used the eval technique to load it into the current shell instead as it doesn't set LD_AUDIT.
May I ask what LD_AUDIT is used for... ie. why is it set? I currently just unset it globally for my flox environments and am wondering if I'm silently breaking...
Makes sense to me. Thank you for the clarification!
I think I just ran into this while checking my neovim setup in a flox environment. The environment was empty except for the neovim nix package. I discovered the issue...
It was not in a container. It was a flox environment on a Debian system using 1.0.1 and activated with the same.
Hey @ericcancil, thanks for using consul-template and taking the time to report this issue. That is definitely a temp file, it is used to make the write atomic by writing...
I'm also seeing this. I have no pinned versions and no 'pkg-group' fields defined (only pkg-path). ```sh $ flox list [..] helix: helix (25.01.1) [..] $ flox show helix helix...
Just hit this again with aider-chat. Had to add a pkg-group entry for it to get it to upgrade to the latest version.
Moving the package to the examples area would be a great idea. Right now, when working off the examples to help understand the package, using this type initially looks like...