Bug 1663028

Summary:	rh-nodejs10: 'npm install' fails with Z_DATA_ERROR
Product:	Red Hat Software Collections	Reporter:	Jon Dufresne <jon.dufresne>
Component:	rh-nodejs10	Assignee:	Zuzana Svetlikova <zsvetlik>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rh-nodejs10	CC:	sipunk
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-25 14:51:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jon Dufresne 2019-01-02 18:24:33 UTC

Note: The component is wrong as rh-nodejs10 doesn't exist as a component.

Description of problem:

After installing the SCL rh-nodejs10, the command `npm install` fails with the error: Z_DATA_ERROR.

Version-Release number of selected component (if applicable):

rh-nodejs10-3.2-2.el7.x86_64


How reproducible:

100%


Steps to Reproduce:
1. Clean working directory with a NPM shrinkwrap file
2. Clean npm cache (npm cache clean -f)
3. Clean `~/.npm` directory
4. Run command `scl enable rh-nodejs10 -- npm install`


Actual results:

npm ERR! code Z_DATA_ERROR
npm ERR! errno -3
npm ERR! invalid distance too far back


Expected results:

Packages installed to node_modules.


Additional info:

As a workaround, the command `npm ci` works.

Comment 1 Zuzana Svetlikova 2019-01-03 12:54:30 UTC

I did not manage to reproduce it. I tried installing packages both from npm repository and locally cloned repo, but it succeeded in both cases.

Comment 2 Jason Cooper 2019-02-12 21:54:31 UTC

I run into the same error, but it's when I run the audit command (scl enable rh-nodejs10 "npm audit") after running "npm install". It only happens in the branch of my project where I have plotly.js as a dependency.

I'm running CentOS 7.6.1810 (Core).

Comment 3 Zuzana Svetlikova 2019-02-25 14:51:53 UTC


*** This bug has been marked as a duplicate of bug 1677710 ***