Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 15 04:15
    dependabot[bot] labeled #510
  • Jan 15 04:15
    dependabot[bot] opened #510
  • Jan 15 04:15

    dependabot[bot] on npm_and_yarn

    chore(deps-dev): bump shelljs f… (compare)

  • Dec 30 2021 21:25
    ifishnet starred ArcBlock/forge-js
  • Dec 08 2021 20:53
    StoatPower starred ArcBlock/forge-elixir-sdk
  • Nov 30 2021 08:36
    kevinkang131419 starred ArcBlock/forge-cli
  • Nov 04 2021 01:35
    dietmerc starred ArcBlock/forge-js
  • Sep 21 2021 03:12
    dependabot[bot] labeled #509
  • Sep 21 2021 03:12
    dependabot[bot] opened #509
  • Sep 21 2021 03:12

    dependabot[bot] on npm_and_yarn

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

  • Sep 01 2021 04:52

    dependabot[bot] on npm_and_yarn

    (compare)

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

    dependabot[bot] on npm_and_yarn

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

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

    dependabot[bot] on npm_and_yarn

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

  • Aug 11 2021 02:04
    dependabot[bot] labeled #401
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
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.