I was able to do two transfers without problems, but the third one shows this error:
4 Likes
Hi @digipl, thanks for the report.
We saw something similar yesterday, but with counter 2, so I suspect that the client is out of sync somehow, but not sure yet. I’m unfortunately out of town now but will try get time to have a look this weekend.
14 Likes
We’ve seen that a couple times too @digipl.
This is happening due to an out of order transfer. We’re not 100% sure if this is a) because we didn’t get the correct history at the client before sending, or b) the elders themselves are out of sync. Investigating though!
edit: Ah, @oetyng is a ninja!
16 Likes
The error occurs after a ^C.
The third transfer was taking a long time (more than 10 seconds) and I thought the program had failed.
I imagine that the first TX-ID =1 instead of 0 because I used that key to create a new safekey.
6 Likes
Updated the OP to make this the recommended method 
10 Likes
Who can tell for regular person what does this testnet show? How it looks?
3 Likes
@tfa 
…
3 Likes
For someone who has been around since 2017, but not understanding the updates, how far away is this testnet from fleming? What components are we testing and what is missing?
16 Likes
I think we will see beta at the latest in 2027…
… Let me see the price below 20c again please, please! 
2 Likes
You are @zeroflaw in disguise and i want my socks back!!!
1 Like
Meanwhile, at other project I watch, they plan to release Android compilation target before christmas:
https://gitter.im/red/red?at=5fdca5e997312f4b6bd69ea9
And the answer is:
Ah, Christmas, a time for technology to disrupt families. ;^)
TRULY!
On Mac, I initially encountered a tar:Unrecognized archive format and tar:Error exit delayed from previous errors issue. But the .safe folder was created in the home directory along with an empty cli folder within it.
So I unzipped the cli app (from GitHub) and added it to the empty cli folder within the .safe folder. After that, everything worked as described including all commands. It just works indeed. I also like how automatically well organized all the created folders and subfolders are (very easy to find things compared to previous iterations). Very stable resource usage, etc.
This is excellent. Well done to the entire @maidsafe team.
17 Likes
Are folks a able to upload? I can’t do safe file put ./directory/ --recursive so far. I’ve had other CLI errors intermittently, but that one is permanent.
5 Likes
If you or anyone manage to store data let me know so I can see what PUT and GET look like in the logs. I’m updating vdash today.
7 Likes
I have this working on my local net. I’ll check logs when at home.
2 Likes
I had that, but stopping/starting things seemed to fix it in the end.
4 Likes
I have most of the features working in vdash and think I know what to use for GET / PUT, which seems to be the trace!() here:
https://github.com/maidsafe/sn_node/blob/master/src/node/adult_duties/chunks/mod.rs#L43
I’ve also found an INFO message with “Writing chunk succeeded!” but am not sure if that’s suitable (maybe too general or not general enough?). I want to count GETS which may qualify for a reward, and corresponding PUTS for rewardable data.
However, I can’t get sn_node.log to include any TRACE output (I have INFO or ERROR only) using the following:
RUST_LOG="sn_node=trace,safe=trace" safe node run-baby-fleming -t
But maybe there aren’t many things which would do TRACE?
@StephenC [No hurry, I don’t want to disturb your family life, relaxing, drinking etc. ] can you check for me the best way to count GET and PUT for vdash, and if it is a TRACE message, confirm if the above is the correct incantation. If there are INFO messages I can use for this, let me know. It’s hard for me to be sure while I’m unable to get safe files put working.
6 Likes
The network is not yet ready for that. I get the same error encountered by others (Could not get history for key PublicKey::Ed25519(…)). I get this error systematically, maybe it is because my conditions are different:
-
I build sn_node and sn_api from source
-
I use one VM for each node in a multipass local network (from Canonical)
-
I set explicitly the IP address when launching nodes
-
I use 10 nodes (which is the recommended section size in sn_routing)
Another problem is that I cannot create an account from a secret key. I get the error: Please use --test-coins option, other options not implemented yet. I need this to pre-generate a set of invites. Note: Option --test-coins works but not option --sk.
Also I am not ready and I need time because there many things I would like to implement and test.
So, no need to hurry up. Let the team have some rest during the holiday season and deliver a test network next year.
7 Likes
For those getting the (Could not get history for key PublicKey::Ed25519(…)) error when trying to upload files, it’s worth trying the following, there is a known issue and this is a work around for the moment:
7 Likes