Created
June 24, 2019 19:49
-
-
Save wanderingstan/4e9c797dfe05182ed95ee754ee14a938 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ~/code/HOPCoin-docker-test/client$ docker-compose up | |
| WARNING: The PRISMA_ENDPOINT variable is not set. Defaulting to a blank string. | |
| WARNING: The FRONTEND_URL variable is not set. Defaulting to a blank string. | |
| WARNING: The SENDGRID_API_KEY variable is not set. Defaulting to a blank string. | |
| WARNING: The MAIL_FROM_ADDRESS variable is not set. Defaulting to a blank string. | |
| Recreating hopcoin-docker-test_client_1 ... | |
| hopcoin-docker-test_postgres-db_1 is up-to-date | |
| hopcoin-docker-test_backend_1 is up-to-date | |
| Recreating hopcoin-docker-test_client_1 ... done | |
| Starting hopcoin-docker-test_prisma_1 ... done | |
| Recreating hopcoin-docker-test_api_1 ... done | |
| Attaching to hopcoin-docker-test_postgres-db_1, hopcoin-docker-test_backend_1, hopcoin-docker-test_storybook_1, hopcoin-docker-test_prisma_1, hopcoin-docker-test_client_1, hopcoin-docker-test_api_1 | |
| postgres-db_1 | 2019-06-24 19:38:44.783 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 | |
| postgres-db_1 | 2019-06-24 19:38:44.783 UTC [1] LOG: listening on IPv6 address "::", port 5432 | |
| postgres-db_1 | 2019-06-24 19:38:44.786 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" | |
| postgres-db_1 | 2019-06-24 19:38:44.800 UTC [24] LOG: database system was shut down at 2019-06-24 19:38:37 UTC | |
| postgres-db_1 | 2019-06-24 19:38:44.812 UTC [1] LOG: database system is ready to accept connections | |
| backend_1 | | |
| backend_1 | > [email protected] deploy /home/node/app | |
| backend_1 | > node scripts/deploy.js | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | npx: installed 591 in 43.422s | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 15.381s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | npx: installed 591 in 13.984s | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 14.352s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | npx: installed 591 in 13.891s | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 14.336s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | npx: installed 591 in 13.739s | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 13.83s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 13.425s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | npx: installed 591 in 14.348s | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 14.555s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 13.858s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 21.259s | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 17.905s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| backend_1 | npx: installed 591 in 14.282s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| backend_1 | Deploying Prisma schema... | |
| storybook_1 | | |
| storybook_1 | > [email protected] storybook /home/node/app | |
| storybook_1 | > start-storybook -p 50020 | |
| storybook_1 | | |
| storybook_1 | info @storybook/react v5.1.9 | |
| storybook_1 | info | |
| storybook_1 | info => Loading presets | |
| storybook_1 | info => Loading presets | |
| storybook_1 | info => Loading custom babel config | |
| storybook_1 | info => Loading custom babel config | |
| storybook_1 | info => Using default webpack setup. | |
| storybook_1 | info => Using base config because react-scripts is not installed. | |
| storybook_1 | 10% building 0/1 modules 1 active multi /home/node/app/node_modules/@storybook/core/dist/server/common/polyfills.js /home/node/app/node_modules/@storybook/core/dist/server/preview/gl 69% building 661/665 modules 4 active /home/node/webpack built 117e391241b305e3500d in 26876ms | |
| storybook_1 | ╭─────────────────────────────────────────────────╮ | |
| storybook_1 | │ │ | |
| storybook_1 | │ Storybook 5.1.9 started │ | |
| storybook_1 | │ 41 s for manager and 40 s for preview │ | |
| storybook_1 | │ │ | |
| storybook_1 | │ Local: http://localhost:50020/ │ | |
| storybook_1 | │ On your network: http://172.23.0.2:50020/ │ | |
| storybook_1 | │ │ | |
| storybook_1 | ╰─────────────────────────────────────────────────╯ | |
| api_1 | | |
| api_1 | > [email protected] dev /home/node/app | |
| api_1 | > npx npm-run-all --parallel start playground | |
| api_1 | | |
| client_1 | | |
| client_1 | > [email protected] dev /home/node/app | |
| client_1 | > node server.js | |
| client_1 | | |
| backend_1 | npx: installed 591 in 13.875s | |
| backend_1 | | |
| backend_1 | Cannot connect to Prisma to deploy... trying again in 5 seconds... | |
| prisma_1 | No log level set, defaulting to INFO. | |
| prisma_1 | [INFO] {} - Started. | |
| postgres-db_1 | 2019-06-24 19:45:31.919 UTC [33] ERROR: database "prisma" already exists | |
| postgres-db_1 | 2019-06-24 19:45:31.919 UTC [33] STATEMENT: CREATE DATABASE "prisma" | |
| api_1 | npx: installed 58 in 6.37s | |
| api_1 | | |
| api_1 | > [email protected] playground /home/node/app | |
| api_1 | > npx graphql playground --port 3001 | |
| api_1 | | |
| api_1 | | |
| api_1 | > [email protected] start /home/node/app | |
| api_1 | > npx nodemon -e js,graphql -x node src/index.js | |
| api_1 | | |
| prisma_1 | [INFO] Initializing workers... | |
| prisma_1 | [INFO] Obtaining exclusive agent lock... | |
| prisma_1 | [INFO] Successfully started 1 workers. | |
| prisma_1 | [INFO] Obtaining exclusive agent lock... Successful. | |
| backend_1 | Deploying Prisma schema... | |
| prisma_1 | [INFO] Deployment worker initialization complete. | |
| prisma_1 | Server running on :4466 | |
| api_1 | npx: installed 2 in 3.952s | |
| api_1 | command not found: graphql | |
| api_1 | npm ERR! code ELIFECYCLE | |
| api_1 | npm ERR! errno 1 | |
| api_1 | npm ERR! [email protected] playground: `npx graphql playground --port 3001` | |
| api_1 | npm ERR! Exit status 1 | |
| api_1 | npm ERR! | |
| api_1 | npm ERR! Failed at the [email protected] playground script. | |
| api_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
| api_1 | npm WARN Local package.json exists, but node_modules missing, did you mean to install? | |
| api_1 | | |
| api_1 | npm ERR! A complete log of this run can be found in: | |
| api_1 | npm ERR! /root/.npm/_logs/2019-06-24T19_45_38_007Z-debug.log | |
| api_1 | ERROR: "playground" exited with 1. | |
| api_1 | npm ERR! code ELIFECYCLE | |
| api_1 | npm ERR! errno 1 | |
| api_1 | npm ERR! [email protected] dev: `npx npm-run-all --parallel start playground` | |
| api_1 | npm ERR! Exit status 1 | |
| api_1 | npm ERR! | |
| api_1 | npm ERR! Failed at the [email protected] dev script. | |
| api_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
| api_1 | npm WARN Local package.json exists, but node_modules missing, did you mean to install? | |
| api_1 | | |
| api_1 | npm ERR! A complete log of this run can be found in: | |
| api_1 | npm ERR! /root/.npm/_logs/2019-06-24T19_45_38_243Z-debug.log | |
| hopcoin-docker-test_api_1 exited with code 1 | |
| client_1 | > Using external babel configuration | |
| client_1 | > Location: "/home/node/app/.babelrc" | |
| client_1 | SentryError: Invalid Dsn | |
| client_1 | at new SentryError (/home/node/app/node_modules/@sentry/utils/dist/error.js:8:28) | |
| client_1 | at Dsn._fromString (/home/node/app/node_modules/@sentry/core/dist/dsn.js:40:19) | |
| client_1 | at new Dsn (/home/node/app/node_modules/@sentry/core/dist/dsn.js:13:18) | |
| client_1 | at NodeBackend._setupTransport (/home/node/app/node_modules/@sentry/node/dist/backend.js:26:19) | |
| client_1 | at NodeBackend.BaseBackend (/home/node/app/node_modules/@sentry/core/dist/basebackend.js:15:32) | |
| client_1 | at new NodeBackend (/home/node/app/node_modules/@sentry/node/dist/backend.js:15:42) | |
| client_1 | at NodeClient.BaseClient (/home/node/app/node_modules/@sentry/core/dist/baseclient.js:48:25) | |
| client_1 | at new NodeClient (/home/node/app/node_modules/@sentry/node/dist/client.js:19:23) | |
| client_1 | at Object.initAndBind (/home/node/app/node_modules/@sentry/core/dist/sdk.js:15:38) | |
| client_1 | at Object.init (/home/node/app/node_modules/@sentry/node/dist/sdk.js:93:12) | |
| client_1 | at module.exports (/home/node/app/util/sentry.js:33:10) | |
| client_1 | at app.prepare.then (/home/node/app/server.js:26:48) | |
| client_1 | at process._tickCallback (internal/process/next_tick.js:68:7) | |
| client_1 | npm ERR! code ELIFECYCLE | |
| client_1 | npm ERR! errno 1 | |
| client_1 | npm ERR! [email protected] dev: `node server.js` | |
| client_1 | npm ERR! Exit status 1 | |
| client_1 | npm ERR! | |
| client_1 | npm ERR! Failed at the [email protected] dev script. | |
| client_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
| client_1 | | |
| client_1 | npm ERR! A complete log of this run can be found in: | |
| client_1 | npm ERR! /root/.npm/_logs/2019-06-24T19_45_52_209Z-debug.log | |
| hopcoin-docker-test_client_1 exited with code 1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment