-
-
Notifications
You must be signed in to change notification settings - Fork 14.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
buildNodePackage produces ENOTCACHED
when referring to the same package via different hashes (?)
#223964
Comments
This should be fixed by #214454 and another branch that I don't think has been PR'd yet I'll try to get through those and get the fixes merged in the next few days (the FOD for |
Is there any workaround in the meantime until #214454 is merged? |
Can you test what I've pushed to that PR now? I just pulled in that commit from that other branch and made some fixups, so it would be helpful to get testers. Thank you! |
@oddlama Do you have a working derivation for running immich on NixOS? I'm looking into setting it up |
Describe the bug
When a
package-lock.json
file contains references to the same package and version but by using a different hashing algorithm (e.g. sha1 and sha512), the subsequentnpm build
invocation in the sandbox seems to only find one of them, raising anENOTCACHED
error for the other.Steps To Reproduce
try to build the contained derivation and the following error will appear:
The corresponding multiple definitions that can be found for color-name-1.1.3 in the lockfile are:
Nonetheless, both files seem to be available:
Regenerating the lockfile (and thus replacing all hashing algorithms with sha512) "fixes" the issue, or more likely works around it.
Expected behavior
The original package-lock file should work without modifications.
Notify maintainers
@winterqt
The text was updated successfully, but these errors were encountered: