Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 30 08:36
    kevinkang131419 starred ArcBlock/forge-cli
  • Nov 04 01:35
    dietmerc starred ArcBlock/forge-js
  • Sep 21 03:12
    dependabot[bot] labeled #509
  • Sep 21 03:12
    dependabot[bot] opened #509
  • Sep 21 03:12

    dependabot[bot] on npm_and_yarn

    chore(deps): bump tmpl from 1.0… (compare)

  • Sep 01 04:52

    dependabot[bot] on npm_and_yarn

    (compare)

  • Sep 01 04:52
    dependabot[bot] closed #506
  • Sep 01 04:52
    dependabot[bot] commented #506
  • Sep 01 04:52
    dependabot[bot] labeled #508
  • Sep 01 04:52
    dependabot[bot] opened #508
  • Sep 01 04:52

    dependabot[bot] on npm_and_yarn

    chore(deps): bump tar from 4.4.… (compare)

  • Aug 11 03:11
    dependabot[bot] labeled #175
  • Aug 11 03:11
    dependabot[bot] opened #175
  • Aug 11 03:11

    dependabot[bot] on npm_and_yarn

    chore(deps): bump path-parse fr… (compare)

  • Aug 11 02:04
    dependabot[bot] labeled #401
  • Aug 11 02:04
    dependabot[bot] opened #401
  • Aug 11 02:04

    dependabot[bot] on npm_and_yarn

    chore(deps): bump path-parse fr… (compare)

  • Aug 11 00:35
    dependabot[bot] labeled #507
  • Aug 11 00:35
    dependabot[bot] opened #507
  • Aug 11 00:35

    dependabot[bot] on npm_and_yarn

    chore(deps): bump path-parse fr… (compare)

magrook
@magrook
@wangshijun let me know if this needs adding to the github issues list:
forge stop demo-chain
ℹ Stopping demo-chain chain...
⠆ Waiting for chain demo-chain to stop...
✖ kill EPERM
✖ cannot get daemon process info, ensure forge is started!
forge@craig-backbone:~$ forge start demo-chain
ℹ Chain demo-chain is already started!
forge@craig-backbone:~$ forge stop demo-chain
ℹ Stopping demo-chain chain...
🙈 Waiting for chain demo-chain to stop...
✖ kill EPERM
✖ cannot get daemon process info, ensure forge is started!
forge@craig-backbone:~$ forge stop
ℹ Stopping demo-chain chain...
◷ Waiting for chain demo-chain to stop...
✖ kill EPERM
✖ cannot get daemon process info, ensure forge is started!
polunzh
@polunzh
@magrook Could run these two run commands to check the forge processes?
forge ps
ps -ef | grep -v grep | grep -v stop | grep forge
magrook
@magrook

forge ps

Chain: demo-chain v0.38.7
┌───────────────┬──────────┬──────────┬──────────┬──────────┬──────────────────────────────┐
│ Name │ PID │ Uptime │ Memory │ CPU │ Endpoint │
├───────────────┼──────────┼──────────┼──────────┼──────────┼──────────────────────────────┤
│ web │ 28697 │ 6h │ 103 MB │ 0.00 % │ http://127.0.0.1:8210/api
├───────────────┼──────────┼──────────┼──────────┼──────────┼──────────────────────────────┤
│ forge │ 16423 │ 2h │ 180 MB │ 0.00 % │ tcp://127.0.0.1:38210 │
├───────────────┼──────────┼──────────┼──────────┼──────────┼──────────────────────────────┤
│ tendermint │ 16543 │ 2h │ 58.2 MB │ 0.00 % │ - │
└───────────────┴──────────┴──────────┴──────────┴──────────┴──────────────────────────────┘

ps -ef | grep -v grep | grep -v stop | grep forge
root 15850 3574 0 17:02 pts/1 00:00:00 sudo su forge
root 15851 15850 0 17:02 pts/1 00:00:00 su forge
forge 15852 15851 0 17:02 pts/1 00:00:00 bash
forge 16415 1 0 17:11 ? 00:00:00 /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/../../erts-10.4.4/bin/run_erl -daemon /home/forge/.forge_cli/release/forge/0.38.7/tmp/pipe/ /home/forge/.forge_cli/release/forge/0.38.7/tmp/log/ /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/../../erts-10.4.4/bin/erl -noshell -s elixir start_cli -mode embedded -setcookie t58XDFggl4t2wX4zSm765pvTz0EZVy75I1fE24Q1vrsACPtYuYYS8A\=\= -sname forge -config /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/sys -boot /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/start -boot_var RELEASE_LIB /home/forge/.forge_cli/release/forge/0.38.7/lib -args_file /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/vm.args -extra --no-halt
forge 16422 16415 0 17:11 pts/2 00:00:00 sh -c /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/../../erts-10.4.4/bin/erl -noshell -s elixir start_cli -mode embedded -setcookie t58XDFggl4t2wX4zSm765pvTz0EZVy75I1fE24Q1vrsACPtYuYYS8A\=\= -sname forge -config /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/sys -boot /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/start -boot_var RELEASE_LIB /home/forge/.forge_cli/release/forge/0.38.7/lib -args_file /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/vm.args -extra --no-halt
forge 16423 16422 0 17:11 pts/2 00:00:44 /home/forge/.forge_cli/release/forge/0.38.7/erts-10.4.4/bin/beam.smp -K true -SDio 64 -sub true -sbwt none -swt low -- -root /home/forge/.forge_cli/release/forge/0.38.7 -progname erl -- -home /home/forge -- -sname forge-forge-35f42098ce85e6defd749fae791ad32d -noshell -s elixir start_cli -mode embedded -setcookie t58XDFggl4t2wX4zSm765pvTz0EZVy75I1fE24Q1vrsACPtYuYYS8A== -sname forge -config /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/sys -boot /home/forge/.forge_cli/release/forge/0.38.7/releases/0.38.7/start -boot_var RELEASE_LIB /home/forge/.forge_cli/release/forge/0.38.7/lib -extra --no-halt
forge 16436 1 0 17:11 ? 00:00:00 /home/forge/.forge_cli/release/forge/0.38.7/erts-10.4.4/bin/epmd -daemon
forge 16440 16423 0 17:11 ? 00:00:00 erl_child_setup 1048576
forge 16525 16440 0 17:11 ? 00:00:00 /home/forge/.forge_cli/release/forge/0.38.7/lib/erlexec-1.10.0/priv/x86_64-unknown-linux-gnu/exec-port
forge 16543 16525 0 17:11 ? 00:00:17 /home/forge/.forge_cli/release/forge/0.38.7/lib/consensus-0.38.7/priv/tendermint/tendermint node --home /home/forge/.forge_chains/forge_demo-chain/forge_release/tendermint
forge 16544 16440 0 17:11 ? 00:00:00 inet_gethost 4
forge 16545 16544 0 17:11 ? 00:00:00 inet_gethost 4
forge 25238 15852 0 19:38 pts/1 00:00:00 ps -ef
craig 28445 1 0 12:38 ? 00:00:00 /home/craig/.forge_cli/release/forge/0.38.7/releases/0.38.7/../../erts-10.4.4/bin/run_erl -daemon /home/craig/.forge_cli/release/forge/0.38.7/tmp/pipe/ /home/craig/.forge_cli/release/forge/0.38.7/tmp/log/ /home/craig/.forge_cli/release/forge/0.38.7/releases/0.38.7/../../erts-10.4.4/bin/erl -noshell -s elixir start_cli -mode embedded -setcookie t58XDFggl4t2wX4zSm765pvTz0EZVy75I1fE24Q1vrsACPtYuYYS8A\=\= -sname forge -config /home/craig/.forge_cli/release/forge/0.38.7/releases/0.38.7/sys -boot /home/craig/.forge_cli/release/forge/0.38.7/releases/0.38.7/start -boot_var RELEASE_LIB /home/craig/.forge_cli/release/forge/0.38.7/lib -args_file /home/craig/.forge_cli/release/forge/0.38.7/releases/0.38.7/vm.args -extra --no-halt
craig 28452 28445 0 12:38 pts/0 00:00:00 sh -c /home/craig/.forge_cli/release/forge/0.38.7/releases/0.38.7/../../erts-10.4.4/bin/erl -noshell -s elixir start_cli -mode embedded -
wangshijun
@wangshijun

@wangshijun - looks like the installer is detecting my OS as CentOS, but I am running Debian - shouldn't this be an Ubuntu release?

this is ok, we are now naming all our linux release as centos, but I will create a ticket for kerner engineers to just naming it linux

@magrook sorry for the latency of the reply, according to the execution logs you sent to me, you may be trying forge-cli with different system users, that will definitely cause a lot of mess.
typically, you can just install cli for yourself (not root, not forge user, just you the normal linux user)
let me know if that works on the machine.
wangshijun
@wangshijun
@magrook I think we spotted the reason of why forge cannot start on Debian OS, new release of forge-cli with the fix is on the way, will notify here once published
magrook
@magrook
@wangshijun awesome, thanks!
polunzh
@polunzh
@magrook
We just released Forge CLI v0.39.12, and passed test on Debian 9.
Upgrade to latest version by npm: npm install @arcblock/forge-cli
polunzh
@polunzh
@magrook Sorry, Install latest version should be: npm install -g @arcblock/forge-cli
Thanks.
magrook
@magrook
@polunzh it looks like since an upgrade that forge asked me to do on Thursday is 0.39.7, and it doesn't seem to want to upgrade via npm - it looks like permission issues on my local box, and using forge install latest claims I have the latest version. I'm going to reinstall the entire thing but I thought I'd mention this here in case it is helpful for you guys to know
Wait a sec, looks like I missed the -g flag, might be no issue here other than the forge install latest output confusing me a little
magrook
@magrook
-
magrook
@magrook
I think there is some contention between yarn and npm - I originall used yarn as per the documentation on the install page - I'm guessing I should wipe and stick with NPM?
magrook
@magrook
Yeah I've got some user specific issues going on for sure, I'm going to wipe clean and start again using only NPM and a specific user to run forge (ArcBlock), with a forge user for the rest (forge) aside from SSL as outlined in the docs and see where I get
polunzh
@polunzh
@magrook
Thanks for your feedback.
In fact, install Forge CLI with npm or yarn is ok, but you should use non-root user.
wangshijun
@wangshijun
@magrook we have a doc for how to install forge-cli with both root and non-root users:https://forge-cli.netlify.com/zh/book/1-introduction/install-forge-cli
but it's Chinese now
magrook
@magrook
@wangshijun @polunzh - I have the demo chain app up and running, pretty cool with the react blocklet!!! However, I am receiving a 504 when attempting to use any session-dependent parts of the demo app (Login, Checkin, Payment). Looks like there's a problem proxying requests between services:
[HPM] Error occurred while trying to proxy request /api/session from localhost:3000 to http://192.168.1.73:3030 (ECONNREFUSED) (https://nodejs.o)
Now, I'm guessing that's because of localhost vs internal IP and my system here not allowing the communication via that port, which I can fix, but I wanted to make sure you guys knew about it just in case the bootstrapping of the application either isn't using localhost OR in the case that those particular demo app options require more than one node to behave themselves properly. I'm assuming this is entirely something on my system but everything else was really smooth in the latest (v0.39.12) so I thought I'd mention it
wangshijun
@wangshijun
@magrook yes, the problem you described above is known to us, if you want to test the blocklet with ABT Wallet, make sure the dapp and ABT Wallet are in the same subnet and the Wallet can access the dapp's IP
when generating dapps, we are not using localhost, we are using the machine's ip address.
magrook
@magrook
@wangshijun Thanks, figured that was probably my issue :) I'll be sorting that out today and then moving on to a PoC for a dapp that might have some value later on
magrook
@magrook
Also re: chinese documentation - google translate did a pretty good job and I was able to use it :)
magrook
@magrook
@wangshijun @polunzh - when running forge install latest under the forge user, it said I was running v0.39.5 and upgraded to v0.39.9 - but it should be v0.39.13 no? I'm just wondering if I have done something wrong with the initial installation as I did manage to get v0.39.12 installed yesterday. I was hoping the upgrade would just be a multiple step process at this stage of development but it does have me a little confused as to why. I'll re-run through the documentation link you provided a couple days ago and see if I can get it sorted, but I thought you'd want to know about this if you didn't already.

forge install latest
ℹ Detected platform is: centos
✔ Latest forge release version: v0.38.9
ℹ Download latest version: v0.38.9.
ℹ Start download https://releases.arcblock.io/forge/0.38.9/forge_centos_amd64.tgz
ℹ Downloading forge_centos_amd64.tgz |████████████████████████████████████████ 100% || 22.87/22.87 MB
ℹ Start download https://releases.arcblock.io/forge/0.38.9/simulator_centos_amd64.tgz
ℹ Downloading simulator_centos_amd64.tgz |████████████████████████████████████████ 100% || 10.17/10.17 MB
ℹ Start download https://releases.arcblock.io/forge/0.38.9/forge_web_centos_amd64.tgz
ℹ Downloading forge_web_centos_amd64.tgz |████████████████████████████████████████ 100% || 23.41/23.41 MB
ℹ Start download https://releases.arcblock.io/forge/0.38.9/forge_starter_centos_amd64.tgz
ℹ Downloading forge_starter_centos_amd64.tgz |████████████████████████████████████████ 100% || 5.30/5.30 MB
ℹ Start download https://releases.arcblock.io/forge/0.38.9/forge_workshop_centos_amd64.tgz
ℹ Downloading forge_workshop_centos_amd64.tgz |████████████████████████████████████████ 100% || 13.82/13.82 MB
ℹ Start download https://releases.arcblock.io/forge/0.38.9/forge_swap_centos_amd64.tgz
ℹ Downloading forge_swap_centos_amd64.tgz |████████████████████████████████████████ 100% || 10.87/10.87 MB
✔ Congratulations! forge v0.38.9 installed successfully!

Now you can create a chain using v0.38.9 with forge chain:create

forge@craig-backbone:/home/craig/demochain-dapp$ forge install latest
ℹ Detected platform is: centos
✔ Latest forge release version: v0.38.9

magrook
@magrook
Perhaps I am missing a service which needs to be started? I have an ABT Wallet on the same subnet (via android app) and the demo dapp starts, but I have the same connection refused error, but I definitely have the port open.
netstat reports nothing listening on that port on the machine I'm working on, which is why I thought perhaps there is a service I've not started. I'll try a few things, the most appropriate looks like the workshop but I was unable to boot that earlier today
magrook
@magrook
On a separate note, the ABTChainNode application is installed, but cannot boot due to missing folders and permission errors - I tried sudo just to see if it would boot but it bails out there too
wangshijun
@wangshijun
@magrook can you give me the output of which forge
magrook
@magrook
Yeah, there are apparently two on my machine, under different users which is probably not helping me:
/home/craig/.npm-packages/bin/forge
and
/usr/local/bin/forge
I followed the docs for each, I'm not sure why I have two separate packages
I'm guessing I need to remove and reinstall everything?
polunzh
@polunzh

@magrook Sorry to bring you trouble.
Does your dApp created base on react-starter blocklet? If so, can you please run with the command, and check its output?

npm run start:server

This command will just start the server.

magrook
@magrook

forge@craig-backbone:/opt/ABTChainNode$ npm run start:server
npm ERR! path /opt/ABTChainNode/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/opt/ABTChainNode/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/forge/.npm/_logs/2019-10-16T02_07_38_497Z-debug.log

And yes, it was a react-starter based dapp
magrook
@magrook
Also @polunzh, It's really no trouble :) I understand what it's like when you are supporting an early version of a platform!
wangshijun
@wangshijun

Yeah, there are apparently two on my machine, under different users which is probably not helping me:

@magrook Maybe it's better to install just one-copy of forge-cli, try to remove one to see if it helps fix the issue.

forge@craig-backbone:/opt/ABTChainNode$ npm run start:server
npm ERR! path /opt/ABTChainNode/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/opt/ABTChainNode/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/forge/.npm/_logs/2019-10-16T02_07_38_497Z-debug.log

About this error, where is your app located, the npm run start:server command should be run in your dapp root directory.

magrook
@magrook
@wangshijun sounds good re: cleanup. Not sure how I managed to get two of the same package installed in different places but I can walk through the docs again, probably helpful to do now that I've been through it once.
re: npm run start:server - here's the output following execution from the dapp directory:

forge-react-starter v0.38.3 ready on http://192.168.1.73:3030
/home/craig/demochain-dapp/node_modules/mongodb/lib/operations/mongo_client_ops.js:474
throw err;
^

MongoNetworkError: failed to connect to server [127.0.0.1:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
at Pool.<anonymous> (/home/craig/demochain-dapp/node_modules/mongodb-core/lib/topologies/server.js:564:11)
at Pool.emit (events.js:193:13)
at Connection.<anonymous> (/home/craig/demochain-dapp/node_modules/mongodb-core/lib/connection/pool.js:317:12)
at Object.onceWrapper (events.js:281:20)
at Connection.emit (events.js:193:13)
at Socket.<anonymous> (/home/craig/demochain-dapp/node_modules/mongodb-core/lib/connection/connection.js:246:50)
at Object.onceWrapper (events.js:281:20)
at Socket.emit (events.js:193:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:81:17)

I'm installing mongo now though I had thought the original installation of the forge packages had done so - I'm guessing the document storage engine for the forge dashboard and chain data is sqlite or something?