search

scryinfo / dp-frontend-old

3 stars 1 forks source link

Errors when running the repo #46

Open chuckume opened 5 years ago

chuckume commented 5 years ago

My : src/Components/Remote.js

const dev = true; export const API = dev ? 'http://localhost:1234' : 'https://dev.scry.info/scry2'; export const Publisher = dev ? 'http://localhost:2222' : 'https://dev.scry.info:443/meta';

Errors appearing docker-compose logs -f

chuck@chuck-XPS-13-9350:~/scry_docker/scry-frontend$ docker-compose logs -f Attaching to scry-frontend_scry-frontend_1 scry-frontend_1 | yarn install v1.10.1 scry-frontend_1 | warning package.json: "dependencies" has dependency "babel-eslint" with range "7.2.3" that collides with a dependency in "devDependencies" of the same name with version "^8.2.2" scry-frontend_1 | warning package.json: "dependencies" has dependency "eslint" with range "4.10.0" that collides with a dependency in "devDependencies" of the same name with version "^4.19.1" scry-frontend_1 | warning package.json: "dependencies" has dependency "eslint-plugin-import" with range "2.8.0" that collides with a dependency in "devDependencies" of the same name with version "^2.9.0" scry-frontend_1 | warning package.json: "dependencies" has dependency "eslint-plugin-jsx-a11y" with range "5.1.1" that collides with a dependency in "devDependencies" of the same name with version "^6.0.3" scry-frontend_1 | warning package.json: "dependencies" has dependency "eslint-plugin-react" with range "7.4.0" that collides with a dependency in "devDependencies" of the same name with version "^7.7.0" scry-frontend_1 | warning latest@0.1.0: "dependencies" has dependency "babel-eslint" with range "7.2.3" that collides with a dependency in "devDependencies" of the same name with version "^8.2.2" scry-frontend_1 | warning latest@0.1.0: "dependencies" has dependency "eslint" with range "4.10.0" that collides with a dependency in "devDependencies" of the same name with version "^4.19.1" scry-frontend_1 | warning latest@0.1.0: "dependencies" has dependency "eslint-plugin-import" with range "2.8.0" that collides with a dependency in "devDependencies" of the same name with version "^2.9.0" scry-frontend_1 | warning latest@0.1.0: "dependencies" has dependency "eslint-plugin-jsx-a11y" with range "5.1.1" that collides with a dependency in "devDependencies" of the same name with version "^6.0.3" scry-frontend_1 | warning latest@0.1.0: "dependencies" has dependency "eslint-plugin-react" with range "7.4.0" that collides with a dependency in "devDependencies" of the same name with version "^7.7.0" scry-frontend_1 | [1/4] Resolving packages... scry-frontend_1 | [2/4] Fetching packages... scry-frontend_1 | error An unexpected error occurred: "https://registry.yarnpkg.com/@material-ui/core/-/core-1.2.1.tgz: 140186766006080:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:469: scry-frontend_1 | ". scry-frontend_1 | info If you think this is a bug, please open a bug report with the information provided in "/home/node/scry-frontend/yarn-error.log". scry-frontend_1 | info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. scry-frontend_1 | info There appears to be trouble with your network connection. Retrying... scry-frontend_1 | info There appears to be trouble with your network connection. Retrying... scry-frontend_1 | info There appears to be trouble with your network connection. Retrying...

hydrandt commented 5 years ago

Problem with registry.yarnpkg.com availability from China. I switched the npm repository to the taobao one (yarn config set registry https://registry.npm.taobao.org), but yarn.lock still points to registry.yarnpkg.com. I replaced it with registry.npm.taobao.org, but some packages versions could not be found there (react-transition-group-2.0.11).

So I removed yarn.lock and started yarn with the Chinese repository. However, I am not sure whether this will not break things - can you comment on this, @mattermoran ?

@chuckume, now it is very slow for me to check with the Chinese mirror, could you please:

  1. git pull this repo to get my changes (on the docker branch)
  2. delete yarn.lock
  3. docker-compose down (in the directory where this repo is cloned)
  4. docker-compose up --build (omiting the -d (detach) - so you will see the logs immediately)