no but I have not had time to look at sn_node 0.44.1 yet
I think so – waiting for authd 0.8.1 install to get fixed
1 Like
Ok cool, thanks. Was trying but no success.
Good to know I’m not alone.
2 Likes
You don’t have to, you can simply create testcoins for your CLI with $ safe keys create --test-coins --for-cli, after that you can upload files to the network.
3 Likes
Should it be working now?
My steps are
rm -rf ~/.safe
curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
safe node install
safe node run-baby-fleming
safe keys create --test-coins --for-cli
then safe keys create just hangs?
Very likely it’s the version of CLI not compatible with node version, we still need to release it, so unless you make sure you use both node and cli versions from Testnet #5 you may have this connectivity issues.
5 Likes
success, much appreciated @bochaco
josh@pc1:~$ safe keys create --test-coins --for-cli
New SafeKey created: "safe://hyryyyybwdkbip7idf7ifjpqkrt6i8zsk14ugjq1q6n1iyscrxycupqzyko"
Preloaded with 1000.111 testcoins
Key pair generated:
Public Key = 341a8356f6a32f6a54b5ca247d53deca96a664ba4ef0a5505984781936bae054
Secret Key = 86c52fc7f929bc9fb46ea8c6297a013e6f2d75a9002f282313598cc219fdabb2
Setting new SafeKey to be used by CLI...
New credentials were successfully stored in /home/josh/.safe/cli/credentials
Safe CLI now has write access to the network
5 Likes
Can you confirm the exact version nos that should work?
1 Like
I think they were CLI v0.26.0 and sn_node 0.36.0
2 Likes
Thank you +chars
1 Like
Another week of github updates… How’s it looking this week 
2 Likes
The version of parts goes up and up silently.
1 Like
@StephenC we miss you 
We should all shout testnet today to lure him out and set expectations 
3 Likes
Not sure how well it is working, but it shows me interesting co-developements in sn_messaging and sn_routing. Seems that the efforts are focusing in increasing the efficiencies in messaging, maybe in order to get the full potential out of the AE principles. It seems to me that the OOM bug is not so much about actual individual errors in code, but more about the complexity of fitting all the parts together after AE implementation.
But the radar, the radar… I’d think that coding and testing is going to take some time still, and I’d say no testnet this week, but who knows, I have been surprised at the speed of team so many times recently, that I would not bet on it.
4 Likes
Still here lurking! 
I suppose now is a good time for an update from HQ - I’ll post in the relevant topic shortly.
14 Likes
@StephenC Right when I am retiring for the night. Sounds very much like an announcement of a testnet to me.
8 Likes
No testnet today @neo , sleep easy!!
13 Likes
Im failing miserably here…
willie@gagarin:~/.safe$ safe -V
sn_cli 0.26.0
willie@gagarin:~/.safe$ safe node bin-version
sn_node 0.36.0
willie@gagarin:~/.safe$ safe keys create --test-coins --for-cli
[sn_client::connections::listeners] ERROR 2021-05-26T17:21:45.978106803 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.9/src/connections/listeners.rs:57] Error while processing incoming message: MessagingProtocol(FailedToParse("Client message payload as Msgpack: invalid type: map, expected a sequence")). Listening for next message...
[sn_client::connections::listeners] ERROR 2021-05-26T17:21:45.980091868 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.9/src/connections/listeners.rs:57] Error while processing incoming message: MessagingProtocol(FailedToParse("Client message payload as Msgpack: invalid type: map, expected a sequence")). Listening for next message...
[sn_client::connections::listeners] ERROR 2021-05-26T17:21:45.980387548 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.9/src/connections/listeners.rs:57] Error while processing incoming message: MessagingProtocol(FailedToParse("Client message payload as Msgpack: invalid type: map, expected a sequence")). Listening for next message...
My node is 0.42.6 cli 0.26.0
2 Likes
that’s the CLI not being up to date w/ the latest client/sn_messaging again. (we should clarify this err)
4 Likes
Not an official update - just a quick note for anyone reading to say we’ve got a few key absences today that IMO take a potential testnet release off the table. I would say we should also rule out a Friday release so I’m looking to next week now.
We’ve got a team meeting this afternoon where I’ll get fully up to speed with where everyone else is, then I’ll post into the official updates thread to keep everyone informed. Thanks all
30 Likes