-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
add path to 'very large path' error #4608
Conversation
Interesting, I hadn't been aware of this PR when opening #4625! Guess that's an alternative, and both ways make reasonable sense to me — I kind of like #4625 just because it adds metadata, thus hopefully opening the way for other improved diagnostics, but OTOH it's quite a bit more code so I guess some balance will have to be found :) Something I think is missing from here is the fact that currently the logic is to display the warning only once. I changed said logic in this part, this part, this part and this part of my PR if I'm not missing any. |
@edolstra what's missing here? |
@edolstra would be great to know if this is a good way forward to debug these warnings. |
I marked this as stale due to inactivity. → More info |
It would be really great to have some way to debug this. I'm not a seasoned NixOS user, and I was trying to install it on a 16GB machine, and I can't tell what is making the
|
Passing the option |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-03-17-nix-team-meeting-minutes-41/26614/1 |
@Ericson2314 I'm happy to get this branch working again, if it looks like its something that's desired. |
@bburdette Yeah maybe. But perhaps it would be better to put the activities in the underlying implementations? |
I think this is no longer needed because nix/src/libfetchers/input-accessor.cc Line 36 in 02bd821
Do leave a comment if this is not the case! |
This is to address issue #1184, the vague 'dumping very large path' warning. Rather than changing the warning message itself, we're creating an Activity when we copy a path, similar to what happens in store-api.cc.
Here's the output with my test case:
I put in an
isInStore
check before adding the Activity, otherwise there's quite a bit of extra output: