search

pushkin-consortium / pushkin-cli

A CLI designed to facilitate the setup process of a Pushkin stack
MIT License
0 stars 4 forks source link

Problems with yarn.lock #66

Closed jkhartshorne closed 4 years ago

jkhartshorne commented 4 years ago

Ideally, we'd copy the local yarn.lock to the Docker container in order to ensure we are using exactly the same dependencies during production. However, doing so resulted in this weird error:

error Integrity check failed for "basic_web" (computed integrity doesn't match our records, got "sha512-HffYVRHj62f01qlazruJl+vWWYsIv65VoxS1Tpu7KuQD2hpmPunTbPVwKhwWnLjGI5xmyc7VTwKConsE/u6oZQ== sha1-W+Gzd8/Grk20KB/Q65LuV99wJBg=") info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. ERROR: Service 'server' failed to build: The command '/bin/sh -c yarn install --production' returned a non-zero code: 1

Note that basic_web refers to the web dependencies of an experiment named basic.

I have simply removed copying the yarn.lock file from the dockerfile, but again that seems not ideal.

jkhartshorne commented 4 years ago

Hmmm. Haven't been able to replicate this since.

jkhartshorne commented 4 years ago

OK, this is now recurring. This has something to do with the yarn lockfile. It seems that the local tempPackages packages don't have integrity checksums. And that (probably?) causes problems. I'm not sure how to address it yet.