Github messages for voidlinux
 help / color / mirror / Atom feed
From: rmccask <rmccask@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: llhttp: update to 2.0.5
Date: Tue, 12 May 2020 19:39:44 +0200	[thread overview]
Message-ID: <20200512173944.pRXFIqJi5Hg-srVCJXrRrnxMuCebjBfvqmURs4538s8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21744@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

New comment by rmccask on void-packages repository

https://github.com/void-linux/void-packages/pull/21744#issuecomment-627490352

Comment:
I see a lot of errors mentioning "npm ERR! cb() never called".  You could wait for a new node package since it is being worked on but I don't think it should be necessary.  A couple of suggestions I saw:

```
If you have npm version 5 or above, try this first:

$ sudo npm cache verify

Otherwise:

$ sudo npm cache clean
```

Another suggestion said that uninstalling the node package, rebooting and then reinstalling fixed it.  I suspect that just cleared it out of memory but you could try it.  Please let me know if either of these works.

  parent reply	other threads:[~2020-05-12 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 13:03 [PR PATCH] " rmccask
2020-05-11 18:28 ` [PR PATCH] [Merged]: " Hoshpak
2020-05-12 10:20 ` mustaqimM
2020-05-12 11:48 ` rmccask
2020-05-12 12:39 ` mustaqimM
2020-05-12 12:48 ` rmccask
2020-05-12 12:49 ` rmccask
2020-05-12 17:15 ` oliver-cfc
2020-05-12 17:17 ` oliver-cfc
2020-05-12 17:39 ` rmccask [this message]
2020-05-12 18:06 ` oliver-cfc
2020-05-12 19:12 ` rmccask
2020-05-13  1:01 ` rmccask
2020-05-13  7:15 ` mustaqimM
2020-05-13 12:29 ` rmccask
2020-05-13 12:38 ` mustaqimM
2020-05-14 15:55 ` oliver-cfc
2020-05-28 14:37 ` nathanblair

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200512173944.pRXFIqJi5Hg-srVCJXrRrnxMuCebjBfvqmURs4538s8@z \
    --to=rmccask@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).