Error running yarn external-services up --detach about hash HOT 10 CLOSED

Hi @sstchur - can you verify that Docker is running?

Please enter docker ps in your terminal:

• it should give you a table containing CONTAINER ID and some other things.
• if Docker isn't running, it'll say something like "Cannot connect to the Docker daemon".

If Docker isn't running, starting it depends on how you've installed it:

• if you've installed the Docker desktop client, you'll have to launch that.
• otherwise, sudo systemctl start docker might do the trick.

If you let me know how you get on with that I can advise further.

from hash.

So after starting up and a variety of messages like

[dev:frontend] This problem is likely caused by another plugin injecting
[dev:frontend] "SpinnerIcon" without registering it in the scope tracker. If you are the author
[dev:frontend]  of that plugin, please use "scope.registerDeclaration(declarationPath)".
[dev:frontend] The exported identifier "HashIcon" is not declared in Babel's scope tracker
[dev:frontend] as a JavaScript value binding, and "@babel/plugin-transform-typescript"
[dev:frontend] never encountered it as a TypeScript type declaration.
[dev:frontend] It will be treated as a JavaScript value.

I now see:

[dev:backend:*realtime] info: Updated ownership of slot "realtime" {"service":"realtime","instanceId":"d8d911e6-3bda-4430-b440-3ec70a57beda","timestamp":"2022-02-17T15:56:00.712Z"}
[dev:backend:*realtime] info: Updated ownership of slot "realtime" {"service":"realtime","instanceId":"d8d911e6-3bda-4430-b440-3ec70a57beda","timestamp":"2022-02-17T15:56:05.707Z"}
[dev:backend:*realtime] info: Updated ownership of slot "realtime" {"service":"realtime","instanceId":"d8d911e6-3bda-4430-b440-3ec70a57beda","timestamp":"2022-02-17T15:56:10.720Z"}```

It doesn't seem to indicate what port the local dev server is running on, but I guessed 3000, and when I browse, there I see this (which I think is progress?):

from hash.

Hey, thanks for letting me know. I will try to find some time to try this out. Been out of commission sick this past week. But will try to find some time in the next few days.

I actually did get HASH to run quite a while back, but never updated this thread. Last time I managed to get to run though, it was so painfully slow as to mostly be useless. Not sure if I did something wrong. Happy to try it again now that there have been updates.

from hash.

Thanks for the help! Docker was not in fact running. sudo systemctl start docker did not work (I got the error "System has not been booted with systemd as init system." After doing a bit of research, I learned this is because I'm using the WSL. Apparently I can use the equivalent Sysvinit commands to do the same thing. So I tried sudo service docker start and got "* Starting Docker: docker"

I then ran sudo docker ps and got:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

I then tried yarn external-services up --detach again, but I got several permission denied errors. So then I tried sudo yarn external-services up --detach and what do you know! It appears to be pulling the container code and starting up. It hasn't finished yet, so the jury's still out, but this looks promising.

from hash.

Yep, that’s definitely progress 👍

[dev:frontend] This problem is likely caused by another plugin injecting
[dev:frontend] "SpinnerIcon" without registering it in the scope tracker. If you are the author
[dev:frontend]  of that plugin, please use "scope.registerDeclaration(declarationPath)".

↑ These warnings will be gone when we merge #320 – I hope it will be quite soon! Also we just merged #322, which should give you less noise in the output. Try to git pull; yarn install before running yarn dev again.

Once you run yarn seed-data, you should be able to login as alice or bob. We use email confirmations instead of passwords and these emails are mocked during local dev. See console output once you’ve entered one of the two demo logins 👀

from hash.

Both #320 and #322 are merged now 👀

from hash.

👋 @sstchur! Has the issue been fixed for you?

from hash.

from hash.

Alright, so I finally had some time to pull latest and try again. I can get the docker service running and successfully run yarn external services up --detach. I then ran yarn dev, but I see some errors, and it seems like the frontend service isn't running (it doesn't connect when I try localhost:3000). The output below shows a couple of Errors, like "failed to load next.config.js". Any idea what I might be doing wrong?

[dev:frontend] ready - started server on 0.0.0.0:3000, url: http://localhost:3000
[dev:backend:*search-loader] [INFO] 16:04:48 ts-node-dev ver. 2.0.0-0 (using ts-node ver. 10.4.0, typescript ver. 4.5.5)
[dev:backend:*realtime] [INFO] 16:04:48 ts-node-dev ver. 2.0.0-0 (using ts-node ver. 10.4.0, typescript ver. 4.5.5)
[dev:backend:*api] [INFO] 16:04:48 ts-node-dev ver. 2.0.0-0 (using ts-node ver. 10.4.0, typescript ver. 4.5.5)
[dev:frontend] info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
[dev:frontend] Error: failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
[dev:frontend] TypeError: Cannot read properties of undefined (reading 'version')
[dev:frontend] at Object. (/home/sstchur/dev/hash/node_modules/html-webpack-plugin/lib/file-watcher-api.js:7:67)
[dev:frontend] at Module._compile (node:internal/modules/cjs/loader:1101:14)
[dev:frontend] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
[dev:frontend] at Module.load (node:internal/modules/cjs/loader:981:32)
[dev:frontend] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
[dev:frontend] at Module.require (node:internal/modules/cjs/loader:1005:19)
[dev:frontend] at require (node:internal/modules/cjs/helpers:102:18)
[dev:frontend] at Object. (/home/sstchur/dev/hash/node_modules/html-webpack-plugin/lib/cached-child-compiler.js:41:24)
[dev:frontend] at Module._compile (node:internal/modules/cjs/loader:1101:14)
[dev:frontend] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
[dev:frontend] Exit code: 1
[dev:frontend] Command: /usr/local/bin/node
[dev:frontend] Arguments: /usr/local/lib/node_modules/yarn/lib/cli.js dev
[dev:frontend] Directory: /home/sstchur/dev/hash/packages/hash/frontend
[dev:frontend] Output:
[dev:frontend]
info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[dev:frontend] yarn run dev:frontend exited with code 1
[dev:backend:*realtime] info: STARTED {"service":"realtime","instanceId":"e62f517d-3a09-498e-88c3-aa36814f4037","timestamp":"2022-03-03T00:04:50.018Z"}
[dev:backend:*realtime] info: HTTP server listening on port 3333 {"service":"realtime","instanceId":"e62f517d-3a09-498e-88c3-aa36814f4037","timestamp":"2022-03-03T00:04:50.020Z"}
[dev:backend:*search-loader] Opensearch is not enabled. Shutting down search-loader
[dev:backend:*api] (node:6106) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/sstchur/dev/hash/node_modules/@opensearch-project/opensearch/package.json.
[dev:backend:api] Update this package.json to use a subpath pattern like "./".
[dev:backend:*api] (Use node --trace-deprecation ... to show where the warning was created)
[dev:backend:*api] info: Listening on port 5001 {"service":"api"}
[dev:backend:*api] info: GraphQL path: /graphql {"service":"api"}
[dev:backend:*realtime] info: HTTP server closed {"service":"realtime","instanceId":"5c5f9460-8130-4cd9-a212-29e5a2a75a14","timestamp":"2022-03-03T00:05:19.687Z"}
[dev:backend:*realtime] yarn run dev:backend:realtime exited with code SIGINT

from hash.

👋 @sstchur! We made some changes to how the app runs (including #687 which was just merged this morning). It’d be great to get your feedback if you have time to run HASH locally! You can find the instructions in packages/hash/README.md 🙂

from hash.