Closed GFJHogue closed 3 years ago
There is an issue thread on the yarn repo where it says this can be due to
https://github.com/yarnpkg/yarn/issues/2976
I can't reproduce this locally so hard to say. Maybe we leave this open until we can find a proper fix
Also, we can't replace git+https to git+ssh because we get issue reports saying peoples firewalls block ssh
A real ideal would be replacing this old jszlib dependency but that will take a little work, probably replace with pako
Also, it is unclear whether this is the jszlib thing or just mystery thing, that is just the only dependency that explicitly points to a github repo but there are other things that could be using hashes in the dependency tree
I think both @hans-vg and @GFJHogue confirmed this fixed their local workflow (yay)
closing for now
setup.log
Full
setup.sh
output at line 356 and onward https://travis-ci.com/github/LincolnSteinLab/gdc-viewer/builds/198342967Noticed this when my Travis tests started failing.
Testing locally, I was able to reproduce this issue by running
npm install yarn
followed bynode_modules/.bin/yarn install
as per https://github.com/GMOD/jbrowse/blob/b8324df0033796b6d502696dc65c9ff888aae2f3/setup.sh#L133However installing yarn "globally" with
npm i -g yarn
and runningyarn install
(with same node/yarn versions) works fine for me, so that's my workaround for now.Since I was able to reproduce with JBrowse 1.16.6 & 1.16.10, I'm guessing a hash changed for something in
yarn.lock
.