Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 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)

  • Aug 04 01:26
    dependabot[bot] labeled #174
  • Aug 04 01:26
    dependabot[bot] opened #174
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?
wangshijun
@wangshijun
@magrook The above error message shows that your mongodb server is not running, so the dapp cannot connect to it
Perhaps it should be better if we check the runtime requirements before start the dapp.
@polunzh
polunzh
@polunzh

Perhaps it should be better if we check the runtime requirements before start the dapp.

@magrook We'll do something to make the fatal error more friendly.

magrook
@magrook

npm run start:server
npm ERR! path /home/craig/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/craig/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/craig/.npm/_logs/2019-10-18T01_16_24_943Z-debug.log
npm run start:server
npm ERR! path /home/craig/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/craig/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/craig/.npm/_logs/2019-10-18T01_16_24_943Z-debug.log
craig@craig-backbone:~$ which forge
/home/craig/.npm-packages/bin/forge
craig@craig-backbone:~$ forge start
⚠ There are no chains, please create it by run forge chain:create
forge chain:create
✖ Forge releases not found.

You can either run forge install to get the latest forge release.
Or start node with custom forge release folder:

forge start --release-dir ~/Downloads/forge/
FORGE_RELEASE_DIR=~/Downloads/forge/ forge start

Hi guys, just wanted to ask if this is a known issue with release .14 - I updated my .bashrc so both the forge user and my user are pointed at the same source, then was about to start on a custom dapp PoC to get a better sense on blocklets etc., but after saying yes to the upgrade I cannot seem to get anything to run. I'll re-install probably this evening or tomorrow AM, but I thought this info might be helpful. I'm about to upload the log file too in case you need it
(And please, just let me know if you would rather I file straight into github - I just want to avoid creating annoying duplicate issues for the team)
polunzh
@polunzh
@magrook What do you mean "updated my .bashrc"?
Don't worry about duplicated issue, if it is, we will deal with it, thanks.
magrook
@magrook
@polunzh when I upgraded via npm, it looks like a separate forge was installed in my local dir, /home/craig/.npm-packages/bin/forge
the original was a symlink generated in /usr/local/bin/ forge -> ../share/.config/yarn/global/node_modules/.bin/forge
so my user on debian was using the first forge, the forge user was using that second one, the symlink I pasted in
what I did was change the forge .bashrc config to match my user account to override and ensure I was using the same source package for both users
(^ where forge is the user account on my box)
magrook
@magrook
heya everyone, I have an odd problem happening here

craig@craig-backbone:~$ forge start --dry-run
⚠ There are no chains, please create it by run forge chain:create
craig@craig-backbone:~$ forge chain:create
✖ Forge releases not found.

You can either run forge install to get the latest forge release.
Or start node with custom forge release folder:

forge start --release-dir ~/Downloads/forge/
FORGE_RELEASE_DIR=~/Downloads/forge/ forge start

craig@craig-backbone:~$ forge --version
0.39.15

I've sorted out the version discrepancy and there is only one forge instance being referenced by both users
However, I cannot create a chain due to the error above. I will review github to see if there's any additional info there
Additionally, forge install latest rolls me back to 0.39.2 -> even after I manually updated the release.yml file to point at .15
magrook
@magrook
This one is already in github issues, but I'm currently kind of unable to progress, I will continue to familiarize with underlying source code to see if I can find anything further
magrook
@magrook
It looks to me as though something has been missed in ~/.forge_cli/release