ArcBlock/community

boll007

@boll007

Hi, all

miss U

Jean Chen

@Jeanchen27

Tyr Chen

@tyrchen

magrook

@magrook

Hi all! It's Craig, I am here to assist Matt with a few things :)

Matt M

@robroyhobbs

Hey Craig, thanks for joining. :)

wangshijun

@wangshijun

@magrook welcome! if you have any questions about our products, feel free to post here.

magrook

@magrook

Hiya all, one thing that I thought was interesting from a recent conference was the idea of using bytes for status codes - looks like you have something similar with integers here: https://docs.arcblock.io/forge/latest/core/code.html - the benefit being you can group status type in the first nibble and actual status code in the second. This lets you reduce the amount of data that needs to go across the wire in a distributed system. Just an idea I thought might be interesting for you.

magrook

@magrook

Hi All, before I file a github issue I wanted to make sure it's not something I did:

forge@craig-backbone:~/.forge_chains$ forge start demo-chain
⠉ Waiting for chain demo-chain to start...
✖ Forge start failed: forge is not started within 40 seconds
✖ Forge cannot be successfully started, now exiting...
ℹ Stopping demo-chain chain...
ဝ Waiting for chain demo-chain to stop...
✖ kill EPERM
✖ cannot get daemon process info, ensure forge is started!

ℹ Possible solutions:
──────────────

Cleanup already running forge
Ensure no running forge process that cannot be detected by forge-cli
Run: forge stop demo-chain, to stop forge related processes, then try forge start demo-chain again
Report bug to our engineer
It is very likely that forge cannot be started on your environment
Please run: forge start demo-chain --dry-run
forge@craig-backbone:~/.forge_chains$ forge start demo-chain --dry-run
ℹ Command ```to debug forge starting issue:
──────────────
ERL_AFLAGS="-sname forge-forge-35f42098ce85e6defd749fae791ad32d" FORGE_CONFIG=/home/forge/.forge_chains/forge_demo-chain/forge_release.toml /home/forge/.forge_cli/release/forge/0.38.7/bin/forge start
──────────────

magrook

@magrook

Quite a few deprecated js packages too, as a developer seeing warnings from the package maintainer that say things like "This is very old, do not use" scares me a little haha. I know this is fairly common in node packages but thought I'd mention it just in case there's alternatives to the ones in use later on when there's time

Also looks like I cannot run more than one chain on my node, but I'm guessing that's my problem not the platform

Yeah this looks like a bug to me, but perhaps I've done something in error:

119 forge stop
120 forge start fordchain
121 forge blocklet:use
122 cd /home/forge/.forge_chains/forge_fordchain/demo-dapp && yarn start
123 cd /home/forge/.forge_chains/forge_demo-chain/demo-dapp && yarn start
124 history
^ from my terminal history. I started one chain, then tried to set up the dapp demo against that chain, but it wouldn't let me do it against the chain I created as it said demo-chain didn't exist, but I can run the dapp starter against the custom chain. When I open the browser it shows me that it's running demo-chain.

magrook

@magrook

re: Web interface showing the wrong chain - this is my error, I didn't forge web stop/start. That said the UI (in my opinion) should reflect the state of the currently used chain from the command line

Graphql API page doesn't want to boot on my machine either, I'll check for existing github issues before submitting anything

re: Web interface showing the wrong chain - this is my error, I didn't forge web stop/start. That said the UI (in my opinion) should reflect the state of the currently used chain from the command line

There's already a github issue for this it looks like: ArcBlock/forge-cli#80

wangshijun

@wangshijun

Also looks like I cannot run more than one chain on my node, but I'm guessing that's my problem not the platform

Currently one forge node only supports one chain.

Quite a few deprecated js packages too, as a developer seeing warnings from the package maintainer that say things like "This is very old, do not use" scares me a little haha. I know this is fairly common in node packages but thought I'd mention it just in case there's alternatives to the ones in use later on when there's time

Will record this as issue, but this may take some time to resolve since the dependency chain maybe very long.

@magrook can you give a brief description of your dev environment: forge-cli version, node version, os version, etc

wangshijun

@wangshijun

For the forge start and stop issue, should be easy to fix, but I need a little knowledge of your env.

wangshijun

@wangshijun

and @magrook I send this in case you are not online right now, if you have tried forge-cli days ago, please do a cleanup, and then try to create new chain/ bootstrap dapp again:

here is the command to cleanup: forge stop -a && rm -rf ~/.forge_chains && rm -rf ~/.forge_cli

then: forge install latest

then is the chain create/start/stop steps.

magrook

@magrook

@wangshijun Ok re: one chain per node, thanks

re: JS packages - of course, I totally understand - I just wanted to flag it for you guys for later in case someone else is unnerved when the platform starts getting some more real traction out there with 3rd party developers

@wangshijun:

Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.9.0-8-amd64
Architecture: x86-64

nodejs -v
v11.15.0

Versions of fordchain chain:

forge-core version 0.38.7 on centos
forge-cli version 0.39.5
forge_web 0.38.7
simulator 0.38.7
forge_workshop 0.38.7
✔ app: fordchain version 0.1

magrook

@magrook

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

magrook

@magrook

Looks like I've missed something but I can't seem to find reference to it in the docs. When attempting to start the demo dapp, I have an error thrown:

  throw new Error('APP_TOKEN_SECRET must be set to start the application');
  ^

Now, I can set up a value for that no problem, I just want to make sure I didn't miss something in the initial run through as per the docs - that's what I'm helping out with right now so if I just plain missed something plz let me know , because I know how irritating it can be for nonsensical or duplicate git issues can be at times :)

@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

Where communities thrive

People

Repo info

Activity