git rev-parse's stdout ended before 64 characters were read about npm2nix HOT 9 CLOSED

Strangely, this now works. I'm not sure what was going on before, but I could consistently get that error, for more than one project. Does npm2nix keep a cache of git repos or anything like that?

from npm2nix.

I consistently get this error in npm2nix from nixos-16.03.

Error during fetch: Error fetching git://github.com/NixOS/npm2nix.git#5.12.0 from git: git rev-parse's stdout ended before 64 characters were read
error: could not lock config file /run/user/1000/npm2nix-git-checkout-tabtab116424-23487-17snh8y/node-tabtab/.git/config: No such file or directory
fatal: Could not set 'remote.origin.fetch' to '+refs/heads/*:refs/remotes/origin/*'
error: could not lock config file /run/user/1000/npm2nix-git-checkout-pegjs116424-23487-32r9ec/pegjs/.git/config: No such file or directory
fatal: Could not set 'remote.origin.fetch' to '+refs/heads/*:refs/remotes/origin/*'

from npm2nix.

Is this a dupe of #36?

from npm2nix.

I switched from the npm2nix in 16.03 to nixos-unstable, and it seems to be working now.

from npm2nix.

I'm getting this issue again while running npm2nix on the latest nixos-unstable. @chris-martin have you done something to fix the issue?

from npm2nix.

No, I didn't do anything.

I don't think it matters, though. Even when it finishes running, it doesn't output anything. It seems that everything is blocked by #21.

from npm2nix.

I'm not sure if we're all seeing the same issue but I suspect the problem that I saw was timing related.

If my suspicion is correct then the awful nodejs async API is to blame.

I wish luck to the various people who are currently attempting to update npm2nix for the latest npm developments.

from npm2nix.

Rodney Lorrimar [email protected] writes:

I'm not sure if we're all seeing the same issue but I suspect the
problem that I saw was timing related.

I'll try to fix it, I need npm2nix to work.

from npm2nix.

Closing, using node2nix now.

from npm2nix.