Install Issue about arkb HOT 12 CLOSED

Hello @ries9112 .
We have contacted the redstone team to find out what is going on.
Thanks for pointing this issue out.

Best,
Cedrik.

from arkb.

Hey @ries9112 👋🏼
stream/promises is only available on version 15 and up of NodeJS.

from arkb.

I was able to find the issue, the error was related to a single file deploy and one of the latest changes I did. Sorry about that!

Version 1.1.17 has this bug fixed 🙌🏼

from arkb.

Hello @ries9112 , we have removed the redstone-api module which was causing this issue.

Can you please try now with the latest version? During this update we have removed the @textury scope. So to get the latest version you can simply do arkb without the scope.

Best,
Cedrik

from arkb.

Thank you for the follow-up!

I ran my workflow running npm install -g arkb, but ran into a similar issue of MODULE_NOT_FOUND:

from arkb.

Thanks a lot, and sorry about that!

I can confirm that worked, but yet another issue came up when I ran the code again:

Sorry if I missed something else, a lot I'm still learning 🙂

from arkb.

Hey @ries9112 , I haven't been able to reproduce, but I had this issue on an older version, I'm wondering if you're using the latest arkb. Can you please tell me what version of node -v are you using and also from arkb -v.

Thanks

from arkb.

@cedriking thank you for the follow-up! I think before I was on 15.14.0 when specifying to use version 15.

Now I'm not specifying any version and this is what my GitHub Actions workflow looks like:

name: Automated Backups Cryptovoxels
on: 
  schedule:
    - cron: '0 10 * * *'
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
      - name: npm install
        run: |
          npm install -g arkb
      - name: Run Backups
        run: |
          node -v ; 
          arkb -v ;
          echo "Downloading map info..." ;
          curl -s 'https://www.cryptovoxels.com/api/parcels.json' > CryptoVoxelsArchive/parcels.json ;
          curl -s 'https://www.cryptovoxels.com/api/suburbs.json' > CryptoVoxelsArchive/suburbs.json ;
          curl -s 'https://www.cryptovoxels.com/api/islands.json' > CryptoVoxelsArchive/islands.json ;
          cat CryptoVoxelsArchive/parcels.json | jq '.parcels | .[] | .id' | while read id ;
          do 
            echo "Downloading land parcel info $id..."
            curl -s "https://www.cryptovoxels.com/grid/parcels/$id" > CryptoVoxelsArchive/parcels/$id.json
          done
          echo "Creating zip." ;
          zip -r -q CryptoVoxels-latest-archive.zip CryptoVoxelsArchive ;
          echo "Deploying archive to Arweave." ;
          arkb deploy CryptoVoxels-latest-archive.zip --auto-confirm --wallet arweave-keyfile-f7QsdAM6sBC0UsUp1JoEXT93yMbCAPQIo1uBLhjDGSE.json --tag.Tag-Name=CryptoVoxelsArchive ;

I added the node -v and arkb -v commands. Looks like I'm on node v14.17.5, but it doesn't show me the version for arkb and throws an error:

from arkb.

I just tried running it locally on my M1 macbook air and I ran into one of the issue shown previously on GitHub actions:

I'm on v16.8.0 for node and v1.1.16 for arkb

from arkb.

Ah this is in a repo using github actions! Can I please see that repo, I will be able to reproduce the issue quickly and see what's going on, thanks to just running that source.

from arkb.

I made a new public repo here: https://github.com/ries9112/arkb_install_troubleshooting

This is the same as the one I'm using privately, with the exception of the arweave-keyfile. The issue however happens on the arkb deploy CryptoVoxels-latest-archive.zip --auto-confirm --wallet arweave-keyfile-[key-here].json --tag.Tag-Name=CryptoVoxelsArchive command, which you can't reproduce because I excluded the arweave-keyfile.

The workflow up to that last command works fine, see this run for example: https://github.com/ries9112/arkb_install_troubleshooting/runs/3450479051?check_suite_focus=true

Just ran my private repo with the arkb deploy command, and got the same error that I commented about 12h ago that I'm also getting on my M1 macbook:

Thanks for taking a look!

from arkb.

Thank you! The automated script is back to working now without issues 🙂 thanks for looking into it!

from arkb.