We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I noticed that when dune pkg lock runs, it looks for files in the current directory with a naming scheme similar to an opam-repository:
dune pkg lock
newfstatat(AT_FDCWD, "/home/etienne/src/dune/packages/ocaml/ocaml.4.09.2", 0x7ffe320108b0, 0) = -1 ENOENT (No such file or directory) % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 49.56 0.037018 0 74266 56713 newfstatat 33.63 0.025115 0 56689 56688 readlink
That's a lot of system time, and I don't think we're expecting to see these files to be here.
NB this is from dune pkg lock in the dune tree.
The text was updated successfully, but these errors were encountered:
(I'll investigate to see where these calls come from)
Sorry, something went wrong.
Interesting, it comes from:
OpamFile.OPAM.read_from_string contents ~filename:(Path.to_string path |> OpamFilename.of_string | > OpamFile.make)
Then opam tries to determine the realpath of that argument, and does so by stat'ing the whole directory tree.
realpath
Ouch. I suppose we can just get rid of it here.
emillon
No branches or pull requests
I noticed that when
dune pkg lock
runs, it looks for files in the current directory with a naming scheme similar to an opam-repository:That's a lot of system time, and I don't think we're expecting to see these files to be here.
NB this is from
dune pkg lock
in the dune tree.The text was updated successfully, but these errors were encountered: