Bug 1677710 - rh-nodejs10 npm does not work against repository.
Summary: rh-nodejs10 npm does not work against repository.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-nodejs10
Version: rh-nodejs10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.4
Assignee: Jan Staněk
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
: 1663028 (view as bug list)
Depends On: 1678825
Blocks: 1696153 1700625
TreeView+ depends on / blocked
 
Reported: 2019-02-15 16:19 UTC by Piyush Bhoot
Modified: 2021-01-14 09:19 UTC (History)
11 users (show)

Fixed In Version: rh-nodejs10-nodejs-10.10.0-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1696153 (view as bug list)
Environment:
Last Closed: 2019-06-19 08:26:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Upstream (zlib) fix (1.12 KB, patch)
2019-02-19 13:38 UTC, Jan Staněk 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Github sclorg nodejs-ex issues 212 0 'None' open nodejs-ex app does not work with nodejs v10 2020-02-20 12:20:46 UTC

Internal Links: 1678825

Description Piyush Bhoot 2019-02-15 16:19:36 UTC 
Description of problem:
rh-nodejs10 npm does not work against repository.

Version-Release number of selected component (if applicable):
node -v
v10.10.0

How reproducible:
Always


Steps to Reproduce:
1.scl enable rh-nodejs10 bash
2.npm info pm2


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

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-02-15T16_04_13_921Z-debug.log

Expected results:
show pm2 info

Additional info:

Works as expected on rh-nodejs8 and rh-nodejs10 from nodesource
Comment 1 Jan Staněk 2019-02-19 13:37:17 UTC 
This seems like the same issue the linked GH issue is facing -- namely a bug in older versions of zlib, which the npm from rh-nodejs10 seems to trigger. Also, running `npm info` against randomly selected npm packages revealed that this issue plagues pretty much any package from npm repository, not just pm2 and/or nodejs-ex.

I have managed to isolate the fix in the upstream codebase, applied it to the RHEL 7 version of zlib and managed to run the `npm info` successfully with that. The actual fix of this issue should then probably happen within the zlib package.
Comment 2 Jan Staněk 2019-02-19 13:38:33 UTC 
Created attachment 1536332 [details]
Upstream (zlib) fix
Comment 4 Zuzana Svetlikova 2019-02-25 14:51:53 UTC 
*** Bug 1663028 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.