NPM package version not available: unsupported archive type

maxim_mazurok

ProGet Version 5.2.18 (Build 2)

User getting error:

npm WARN tarball tarball data for node-ipc@http://proget.wtg.zone/npm/Registry/node-ipc/-/node-ipc-9.1.3.tgz (sha512-8RS4RZyS/KMKKYG8mrje+cLxwATe9dBCuOiqKFSWND4oOuKytfuKCiR9yinvhoXF/nGdX/WnbywaUee+9U87zA==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for node-ipc@http://proget.wtg.zone/npm/Registry/node-ipc/-/node-ipc-9.1.3.tgz (sha512-8RS4RZyS/KMKKYG8mrje+cLxwATe9dBCuOiqKFSWND4oOuKytfuKCiR9yinvhoXF/nGdX/WnbywaUee+9U87zA==) seems to be corrupted. Trying again.
npm ERR! code EINTEGRITY
npm ERR! sha512-8RS4RZyS/KMKKYG8mrje+cLxwATe9dBCuOiqKFSWND4oOuKytfuKCiR9yinvhoXF/nGdX/WnbywaUee+9U87zA== integrity checksum failed when using sha512: wanted sha512-8RS4RZyS/KMKKYG8mrje+cLxwATe9dBCuOiqKFSWND4oOuKytfuKCiR9yinvhoXF/nGdX/WnbywaUee+9U87zA== but got sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==. (0 bytes)

http://proget.wtg.zone/feeds/Registry/node-ipc/9.1.2 - exists
http://proget.wtg.zone/feeds/Registry/node-ipc/9.1.3 - doesn't exist, returns 404
http://proget.wtg.zone/feeds/Registry/node-ipc/9.1.4 - exists

The SHA that we're getting is for an empty file. I tried to download http://proget.wtg.zone/npm/Registry/node-ipc/-/node-ipc-9.1.3.tgz manually and it's empty: 0 bytes. So the local cache is not the issue.

Workarounds:

update the package to any other version
use npmjs.com registry (https://registry.npmjs.org/node-ipc/-/node-ipc-9.1.3.tgz works and matches sha)

Also, guys in charge of our ProGet install confirmed that this is an internal ProGet error:

System.InvalidOperationException: unsupported archive type at Inedo.ProGet.WebApplication.SimpleHandlers.PackageFiles.InedoArchiveFactory.Open(Stream stream)

rhessinger

Hi @maxim_mazurok,

Is this a cached package from a connector or did you upload this package directly? Has this version always been a problem or is this new? I think the best option may be to reupload this package or delete it and repull it from your connector (if you are using a connector).

The error you are seeing can happen when a file is also a 0 byte tgz file as well. My guess is that either the file failed to download/upload to ProGet or the zip file contents were quarantined from your local anti-virus.

Thanks,
Rich

maxim_mazurok

Is this a cached package from a connector or did you upload this package directly?

It is a cached package from a connector, we didn't upload this package directly.

Has this version always been a problem or is this new?

This has worked before, as it was added to the lock file with the correct resolved URL and correct SHA, so I believe it's a new issue.

Our guys have fixed the issue somehow, I'll let you know the details of the fix once I have them. Thanks!

maxim_mazurok

This is what fixed the issue:

After pulling the package last week, I deleted it and re-pulled just now

rhessinger

Hi @maxim_mazurok,

I'm glad to hear that repulling the package fixed this. Do you have an anti-virus installed on your ProGet server? Is it possible to check that to see if the package was quarantined?

Thanks,
Rich