BasicEconomyTweaks [Early Technical Beta] [OFFLINE - see new beta test - part deux]

Development Releases
42

Hmm… maybe folks just haven’t been uploading? I started a 6 GB upload a while ago, and my node has been getting more chunks since. Always in the previous testnets I have gotten a few hundred chunks immediately upon joining. But I may have never been this early in the game. Go figure…

43

So, trying to upload data, keep getting this error:

[2024-03-28T13:37:00.373326Z ERROR sn_client::uploader::upload] Encountered error Wallet(QuoteExpired(a32ca1(10100011)..)) when getting store_cost for a32ca1(10100011)..
[2024-03-28T13:37:00.373346Z TRACE sn_client::uploader::upload] Received task result: GetStoreCostErr { xorname: a32ca1(10100011).., get_store_cost_strategy: Cheapest, max_repayments_reached: false }
[2024-03-28T13:37:00.373352Z TRACE sn_client::uploader::upload] GetStoreCostErr for a32ca1(10100011).. , get_store_cost_strategy: Cheapest, max_repayments_reached: false
[2024-03-28T13:37:00.373362Z ERROR sn_client::uploader::upload] Max sequential network failures reached during GetStoreCostErr.
[2024-03-28T13:37:00.373412Z DEBUG sn_client::uploader::upload] Make payment processing loop terminated.

Is it possible that the network is filling up fast enough that from the time I get a quote, and it’s actually trying to be used, it’s no longer within price range?

44

I always delete the Client and Node folders, then run safeup for a clean start

4 Likes
45

Hey, I appreciate the enthusiasm, but soon, I’m hoping to be able to do a whole testnet related to the node manager, at which point the testnet instructions will be updated. Maybe hold off until then?

3 Likes
46

What’s you CLI version?

47

Built with git version: d363c9b / main / d363c9b

Most recent from safeup from the top of this post. My 3 chunk upload just went through, so I’m thinking my theory - that nodes are filling up fast enough that quotes aren’t valid anymore - may be the case?

But my initial test file (200 meg) still wont even start. So I don’t know.

48

There has been a release after this testnet was started. Try with the client specified in the OP:

safeup client --version 0.90.1
1 Like
49

172838 chunks inbound…

2 Likes
50

Yup, that’s what I had, also redid safeup again, still same issue on all but my little 3-chunk file

Win 10.

All of my failed uploads from my windows machine end with:

[2024-03-28T14:03:44.498188Z ERROR sn_client::uploader::upload] Encountered error Wallet(QuoteExpired(422d45(01000010)..)) when getting store_cost for 422d45(01000010)..

with various node names that it refers to.

1 Like
51

@joshuef @qi_ma I have a complaint: When I cancel an upload and restart it, it seems to be starting from the beginning again. A few testnets ago I was able to continue where I left. I want that feature back!

52

@chriso I am getting an error when trying to do safeup node-manager

ubuntu@s00:~$ safeup node-manager
**************************************
*                                    *
*    Installing safenode-manager     *
*                                    *
**************************************
Installing safenode-manager for x86_64-unknown-linux-musl at /home/ubuntu/.local/bin...
Retrieving latest version for safenode-manager...
Installing safenode-manager version 0.7.2...
Error: Release binary https://sn-node-manager.s3.eu-west-2.amazonaws.com/safenode-manager-0.7.2-x86_64-unknown-linux-musl.tar.gz was not found

Location:
    src/install.rs:324:24
53

Thanks for the report! Will look into it. Can you download a binary manually in the mean time?

1 Like
54

Can report downloading the binary straight from github works for linux.

1 Like
55

I downloaded for windows and have it running,

but safeup gives

Installing safenode-manager.exe for x86_64-pc-windows-msvc
Retrieving latest version for safenode-manager…
Installing safenode-manager version 0.7.2…
Error: Release binary https://sn-node-manager.s3.eu-west-2.amazonaws.com/safenode-manager-0.7.2-x86_64-pc-windows-msvc.tar.gz was not found

Location:
src\install.rs:243:24

1 Like
56

Update to windows failing to upload. Strange bug.

I try to upload a file from windows (on a NAT if it matters) and it fails with the QuoteExpired issue.

I put that same file on my linux machine (remote server) and upload it from there no problem.

I then upload the file from windows machine, and it “works” (verifies all the chunks are there, no charge)

I’ve deleted my client dir, re-safeup’ed, re-hit the faucet mutliple times.

 C:\Users\Wes\Downloads> safe --version
sn_cli 0.90.1
1 Like
57

Used the version flag so dropped down a version and it worked fine

58

Thanks. Tends to imply there might be a problem in the release process. Will investigate.

1 Like
60

@maidsafe

Can we update the OP with the new client version? I checked out github and saw there was a 90.2 release 2 hours ago, I did

safeup client --version 0.90.2

On my windows machine that was having trouble uploading and it solved my issues.

***Changing this to make it more different than the post I deleted so I can reply to relevant post…

2 Likes
61

I think there was a mistake though, because I installed the update

safeup client --version 0.90.2

and now checking the balance and downloading tokens works without a problem.

No Safe, no wave.

62

@aatonnomicc @chriso

Just skimmed through 60+ posts - which version of node-manager should I grab?
version 0.7.2 and -version 0.7.1 are not found