Im certain that the first few lines of any upcoming announcement will feature the Holy Mantra
rm -rf $HOME/.safe
Im certain that the first few lines of any upcoming announcement will feature the Holy Mantra
rm -rf $HOME/.safe
Thanks for the info.
I have rebuilt latest sn_node from source, downloaded this new node config and I was waiting patiently at the door (“The network is not accepting nodes right now” …), until I got “Cannot start node due to error: Routing(Network(Connection(TimedOut)))”.
Probably that was too early and they have shutdown the network.
Its been down since last Friday(?) IIRC.
There is a brand new config file on aws. I am trying again.
You not even waiting for the pre update these days …
They have restarted today, then stopped it, then restarted it again a few minutes ago.
Dives right in
Agog-o-meters now back on line with fresh dilithium crystals - Needles and full-travel stops inspected - Slight signs of fatigue cracking but within limits for now
Meanwhile…
V5…today…
…?
We do not expect to release Fleming Testnet v5 today.
We’re very close to completing our full Anti Entropy implementation, possibly finishing this today, while in parallel we are working on finalising some other changes which we hope together will eliminate the data loss issues seen in previous testnets. We want to do some thorough internal testing once this is all put together though, as the changes are fairly widespread, therefore we will not be releasing testnet v5 today.
We will make a decision on releasing tomorrow depending on when we get these changes polished, merged, and tested.
Thanks everyone.
Very good! Next week I have much more time to test
And it’s the right thing to do to allow yourself to do testing first. We want stable software later, not buggy software now.
Sounds good, especially as today I’m trying to get the water or of my fuel system so I can start my engine. As my neighbor said when he asked how things were, “there’s always something” (needs doing on a boat). It’s like software really, so I’m taking a few mins to see what vdash might need.
Good luck MaidSafe, testing this next iteration sounds exciting.
Thanks for the update and all the hard work you guys are doing.
Great! Then I got more time to finish the Graphical User Interface ![]()
Woohoo! Yes, we want to test with all bells and whistles
we’ll done team
I think waiting for a more stable v5 test is better than rushing something out on a Friday. I’m sure no one wants to lose their weekends!
It would be awesome if v5 didn’t have the data loss issues. I think that would show excellent progress ad will let us all have some fun for longer too. That would give positive vibes all around! ![]()
Neither I nor the tadpoles will confirm or deny anything.
Brilliant news, all very exciting. AE, DBCs, what a time to be alive
+1 The only purpose of a testnet is to test the code and find bugs. If there are already known bugs that can be fixed in the mean time then fix them. No need to waste time to spin up a testnet that will be on for just a short time until the bug is fixed and a new testnet needs to be started.