yarnpkg/yarn

An unexpected error occurred: "Commit hash required".

Open

#2.976 geöffnet am 23. März 2017

Auf GitHub ansehen
 (33 Kommentare) (18 Reaktionen) (1 zugewiesene Person)JavaScript (2.731 Forks)batch import
cat-bughelp wantedneeds-confirmationtriaged

Repository-Metriken

Stars
 (41.514 Stars)
PR-Merge-Metriken
 (Keine gemergten PRs in 30 T)

Beschreibung

I've got a project, that has been running fine for months, where suddenly adding/installing eth-lightwallet fails during fetching packages with An unexpected error occurred: "Commit hash required".

Suddenly is defined as between March 21st, 9:51AM CET - March 22nd, 5:30PM CET with a commit that did not touch the package.json or lock files (just a css and html fix)

I've tried:

  • changing node version 7.7.4 and 7.7.1 (on 7.7.1 it worked before without question)
  • removing all caches, npm_modules, lockfiles
  • it fails both on a linux (alpine and debian) ci docker image, and on OSX
  • created a new project and added it. this worked, so it's my dependency set that breaks it
  • it appears to be related to bignumber.js in the dependencies, so tried a lot of different formats in https://github.com/roderik/eth-lightwallet.git
  • added if (!commit) console.log(_this2) to my git-fetcher.js line 113 and installed using yarn add https://github.com/roderik/eth-lightwallet.git --verbose --network-concurrency 1 --force Result: https://gist.github.com/roderik/f5ff6abfcdcdb364f2a5327016317de0 and the error log, but this does not show a reason for the commit hash to be empty
  • it installs fine with npm, so it's my dependencies + yarn

I'm stumped and reverted to yarn install || npm i on my ci, but this is not really the way it's supposed to be.

Contributor Guide