Additionally,
forge install latest rolls me back to 0.39.2 -> even after I manually updated the release.yml file to point at .15
when I installed .15 via npm
npm install -g @arcblock/forge-cli --unsafe-perm
^ that's in my own home directory
However, in the forge user home directory, there is information which allows me to start creating a chain
so removing the .forge-cli and .forge-chains directories, then running forge start does not write the information regarding the release data that I do see under the forge user's home directory:
forge start
✔ initialized tmp dir for forge-cli: /home/craig/.forge_cli/tmp
✔ initialized bin dir for forge-cli: /home/craig/.forge_cli/bin
✔ initialized cache dir for forge-cli: /home/craig/.forge_cli/cache
✔ initialized logs dir for forge-cli: /home/craig/.forge_cli/logs
✔ initialized release dir for forge-cli: /home/craig/.forge_cli/release
✔ Checking new version...
⚠ There are no chains, please create it by run forge chain:create
craig@craig-backbone:~$ cd /home/craig/.forge_cli/release
craig@craig-backbone:~/.forge_cli/release$ ls -al
total 8
drwxr-xr-x 2 craig craig 4096 Oct 18 15:40 .
drwxr-xr-x 7 craig craig 4096 Oct 18 15:40 ..
✔ initialized tmp dir for forge-cli: /home/craig/.forge_cli/tmp
✔ initialized bin dir for forge-cli: /home/craig/.forge_cli/bin
✔ initialized cache dir for forge-cli: /home/craig/.forge_cli/cache
✔ initialized logs dir for forge-cli: /home/craig/.forge_cli/logs
✔ initialized release dir for forge-cli: /home/craig/.forge_cli/release
✔ Checking new version...
⚠ There are no chains, please create it by run forge chain:create
craig@craig-backbone:~$ cd /home/craig/.forge_cli/release
craig@craig-backbone:~/.forge_cli/release$ ls -al
total 8
drwxr-xr-x 2 craig craig 4096 Oct 18 15:40 .
drwxr-xr-x 7 craig craig 4096 Oct 18 15:40 ..
so yeah, even though both users report using 0.39.15 via forge --version, and they are both referencing the exact path for the npm installed packages, if I try to
forge install latest or forge install v0.39.15 I get a version not found error, forge ls:remote is also showing me that the list provided from the remote is capped at 0.39.2
At this point I'm kind of unable to do more experimentation because I cannot create chains on 0.39.15 - which I expect is due to the release folder being empty for my user when I try to do so
I'll look around at the install and init code and see if I can track it down
I'm pretty sure the issue is missing release folders for my specific user but a zoom session would probably be very helpful to make sure a) I didn't do something silly by accident, and b) get a better overall sense of the download and installation process in the source code so I can resolve my own issues (and maybe even help you guys with pull requests in the process)
so I'm guessing it may be an inconsequential discrepancy between the available local versions and the version that is actually in use (which was installed via npm)
@magrook for zoom call, do you live in Seatle? what's your timezone?
@tyrchen
When I try to create a chain with @arcblock/forge-cli@1.0.12 I receive the following error message:
% forge chain:create? Chain Name: my-chain? Token Name: MyToken? Token Symbol: MYT✖ Create new chain failed:✖ ENOENT: no such file or directory, mkdir '/Users/mwhesse/.forge_chains/forge_my-chain/forge_release'
I'm on MacOS 10.14.6 and node 8. I tried to pre-create the directory myself but it seems forge-cli first deletes it and then fails to re-create it.
it's keep spinning ~
I’m really in the hot reload capability provided by ArcBlock, but I could not figure it out how this happen or is coded, do you have some intel on it ?