I thought network saving features were turned off for destructive test. Perhaps this was a further measure to test data reliability?? It is being removed but looks like it was obviously named and added
1 Like
It’s from a test for error recovery that tries to see what happens when the network returns a “failure” (action tried by client did not succeed) and how the client can proceed to recover from the same error.
In such tests which only runs with build feature use-mock-routing(non production code) the client library does not depend on the real routing but instead simulates network replies itself to test various edge case scenarios and assert if the client library behaves in a way that is expected. and the fn set_network_limits is a helper it uses to basically limit network storage pretty much. So cases where the vaults do not want to take any more new data.
In this specific test, the “network failure”(which essentially is a failure returned by the network not the network itself failing) is actually simulated few lines above in the same test.
Then it proceeds to confirm if when such an error is received, does the client library handle it as expected and then later when the network is able to accept more client requests(vaults not full anymore) is the client library able to recover from the previous partial storage.
4 Likes
Thanks for the broad explanation!
4 Likes
@Viv’s answer is correct and complete. Also the commit logs might help or give hints. For e.g:
https://github.com/maidsafe/safe_core/commit/6de785e4b9f1afcfa1aec4189a60cbb37655a31f
4 Likes
Crust arrived at version 0.16.1
4 Likes
5 Likes
Nice catch as always I was just peaking at these last night and it had been a couple days since last commit. On a side note data chains was active, just sayin’
5 Likes
couldn’t a content provider set up a site and load up videos and get safecoin for each view?
Yes that’s what I’ve understood, but I think we’re at least a year away from that functionality, which would of course come “online” only after SafeCoins are being reliably exchanged on the SAFE Network.
1 Like
9 Likes
So what’s in the dev update today :)?
1 Like
Why, you can read about all the details in the dev thread ;p
+1 for a supercool update today 
7 Likes
Routing at version 0.24.1
4 Likes
Some pret test 6 fixes, yummy 
3 Likes
Has there been no official update yesterday ? Or did I just miss it ?
There’s a pinned topic on the front page of the forum. So yes, there was an update.
2 Likes
MaidSafe Dev Update - 12th July 2016 There you go 
3 Likes
“final testing phase tba this week”
That’s a tweet we can speculate on for days can’t we 
. Hope the devs don’t spoil a thing here 
. My view:
- TEST 6 (this week)
- pre_Alpha with installers (within 3 weeks)
- Official release of the Alpha (within 6 weeks) where Maidsafe officially announces they go “live” in several interviews and with installers downloadable from the Maidsafe website.
- Rolling updates going into the Beta phase with test-Safecoin and messenger App activated (next 2 months)
- Going from BETA to The SAFE Network version 1.0
Just my speculation here, I have no sources for this one except from my gut feeling
10 Likes
Thank you for pointing that out!
I was so anxious to read the update I completed missed the “final testing phase tba this week” part.
1 Like
Thanks! Not sure why but I often overlook the pinned topics.
Maybe it’s my human “advertising filter” that hides those topic from me…
4 Likes