search

NixOS / npm2nix

Generate nix expressions to build npm packages
MIT License
57 stars 32 forks source link

git rev-parse's stdout ended before 64 characters were read #39

Closed rvl closed 7 years ago

rvl commented 8 years ago

Hi, npm2nix seems to be failing on the jsbn module, perhaps because it's a git repo type module, but I'm not sure.

git clone git@github.com:NixOS/npm2nix.git
cd npm2nix
nix-shell
rm -rf ~/.npm
node --version > output.txt
git --version >> output.txt
node lib/command.js package.json node-packages-generated.nix >> output.txt 2>&1

Result: output.txt

...
Already on 'master'
Your branch is up-to-date with 'origin/master'.
Error during fetch: Error fetching https://github.com/rynomad/jsbn.git from git: git rev-parse's stdout ended before 64 characters were read

Cheers

rvl commented 8 years ago

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?

chris-martin commented 8 years ago

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/*'
chris-martin commented 8 years ago

Is this a dupe of #36?

chris-martin commented 8 years ago

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

NicolasPetton commented 8 years ago

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

chris-martin commented 8 years ago

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.

rvl commented 8 years ago

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.

NicolasPetton commented 8 years ago

Rodney Lorrimar notifications@github.com 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.

rvl commented 7 years ago

Closing, using node2nix now.