Skip to content

fetchMetadata: sill fetchPackageMetaData error for map-obj@^1.0.1 request to https://registry.npmjs.org/map-obj failed, reason: socket hang up #20979

Description

Version: nodejs 10.2.1
Platform: Linux 4.16.11-1-ARCH

Since nodejs-10.2.0 release I get a lot of problems. After the compilation issue reported 2 days ago, now there are issues during fetch:

.................] - fetchMetadata: sill fetchPackageMetaData error for map-obj@^1.0.1 request to https://registry.npmjs.org/map-obj failed, reason: socket hang up

I need nodejs to build opennebula and since the release of node-10.2.x I can't do my work.
Everything work very well with older version.

Can you plz fix this issue, thx.

Activity

  1. ghost changed the title [-]fetchMetadata: sill fetchPackageMetaData error for map-obj@^1.0.1 request to https://registry.np[/-] [+]fetchMetadata: sill fetchPackageMetaData error for map-obj@^1.0.1 request to https://registry.npmjs.org/map-obj failed, reason: socket hang up[/+] on May 26, 2018
  2. benjamingr commented on May 26, 2018

    @benjamingr
    Member

    @Yann-Kaelig if you install an earlier version of Node.js (10.1.0 for example) does the installation work?

    At the current state of this bug report it is hard for us to diagnose and help you with the issue.

    I have installed map-obj on Node.js latest and haven't seen any issues.

  3. benjamingr commented on May 26, 2018

    @benjamingr
    Member

    @Yann-Kaelig hmm, is there any way you could create a minimal sample of code that reproduces this issue and put it on a GitHub repo?

    A reproducing test case would go a long way helping us figure out what went wrong.

    10.2.1's changelog indicates 3 commits:

    Commits

    • [2a9c83321b] - http: fix res emit close before user finish (Robert Nagy) #20941
    • [0b1ba20fc0] - src: re-integrate headers into node.h (Anna Henningsen) #20939
    • [52f21fbfbc] - test: mark test-zlib.zlib-binding.deflate as flaky (Matheus Marchini) #20935

    The third one is about marking something in our CI, the second one

  4. MylesBorins commented on May 26, 2018

    @MylesBorins
    Contributor
  5. mcollina commented on May 26, 2018

    @mcollina
    SponsorMember

    I can't reproduce the issue on Mac OS X or on top of our Docker image.

  6. MylesBorins commented on May 27, 2018

    @MylesBorins
    Contributor
  7. benjamingr commented on May 27, 2018

    @benjamingr
    Member

    @Yann-Kaelig the output you have pasted doesn't really make it clear if installation is successful or not (other than the warning) - can you please let us know if it works?

    Thanks :)

  8. ghost closed this as completedon May 27, 2018
  9. ghost reopened this on May 28, 2018
  10. MylesBorins commented on May 29, 2018

    @MylesBorins
    Contributor

    digging into the log it looks like something is failing in the node-sass install

    7038 verbose lifecycle node-sass@3.13.1~postinstall: unsafe-perm in lifecycle true
    7039 verbose lifecycle node-sass@3.13.1~postinstall: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/jean-michel/one-release-5.4.12/src/sunstone/public/node_modules/node-sass/node_modules/.bin:/home/jean-michel/one-release-5.4.12/src/sunstone/public/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
    7040 verbose lifecycle node-sass@3.13.1~postinstall: CWD: /home/jean-michel/one-release-5.4.12/src/sunstone/public/node_modules/node-sass
    7041 silly lifecycle node-sass@3.13.1~postinstall: Args: [ '-c', 'node scripts/build.js' ]
    7042 silly lifecycle node-sass@3.13.1~postinstall: Returned: code: 1  signal: null
    7043 info lifecycle node-sass@3.13.1~postinstall: Failed to exec postinstall script
    7044 verbose unlock done using /home/jean-michel/.npm/_locks/staging-6829d8dc8e4b11e8.lock for /home/jean-michel/one-release-5.4.12/src/sunstone/public/node_modules/.staging
    

    What type of system are you using? Can you share a copy of your package.json?

  11. Trott commented on Nov 21, 2018

    @Trott
    Member

    Closing due to non-responsiveness. Feel free to comment and/or re-open if there's more information and more to do here.

  12. OfficialAshwaniBhardwaj commented on Jun 3, 2022

    @OfficialAshwaniBhardwaj

    same issue

  13. locked as resolved and limited conversation to collaborators on Jun 4, 2022
  14. Trott commented on Jun 4, 2022

    @Trott
    Member

    I've locked this issue to avoid further unhelpful "me too" comments. (People experiencing problems can always open new issues.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions