Closed mikeland73 closed 4 weeks ago
@Lagoja @gcurtis made updates we talked about:
Running this, I get:
Warning: Outputs for libiconv@latest are not in lockfile. Fetching store paths from nix
To fix this issue and improve performance, please run `devbox install --fix-missing-store-paths
Are we fetching the store paths at the time that I get this message? Or do I need to run the command with the flag
@Lagoja I need to hide the message when using the flag. Will do.
Should we name the flag --tidy-lockfile? Are missing store paths in the lockfile a problem? I thought it just made things slower.
I like that name. Will change. It gives us flexibility to do more stuff.
missing store paths from lockfile can be a big perf drag, especially if all packages are in cache. If the store paths are missing we end up having to download nixpkgs every time (which adds 40s for each nixpkgs). Particularly painful on CICD because env is fresh every time.
This pull request was deployed and Sentry observed the following issues:
go.jetpack.io/devbox/internal/searcher in execG...
View Issuego.jetpack.io/devbox/internal/devpkg in (*Packa...
View Issuego.jetpack.io/devbox/internal/searcher in execG...
View Issuego.jetpack.io/devbox/internal/searcher in execG...
View IssueDid you find this useful? React with a 👍 or 👎
Summary
Adds new
--tidy-lockfile
flag that can be used with install. It fills in any missing store paths in lockfile, improving future performance.I'm not 100% convinced this works in all cases. My two biggest concerns would be:
How was it tested?