Looks like vaults lost connections for the moment. Just a minute ago.
WARN 11:23:11.471251948 [routing::core core.rs:667] Prepared connection info for PeerId(65ee…) as ec7e…, but already tried as ec7e…
WARN 11:23:58.023084219 [routing::core core.rs:605] Node(e721…) Failed to connect to peer PeerId(65ee…): Error { repr: Custom(Custom { kind: TimedOut, error: StringError("Connect failed. errors: (1 o f 6) Tcp direct connect failed: Zero byte read - EOF reached, grace ful exit. (2 of 6) Tcp hole punching failed: Tcp hole punching time d out without making a successful connection. The following warning s were raised during hole punching: 121 warning(s): (1 of 121) Conn ecting to endpoint 127.0.0.1:35136 failed:
Is there a maximum total file size upload or only a maximum file size upload?
What wil be the maximum upload size of a file when the network is stable?
Files get split into chunks of max 1Mb each. The only limit will be how much safecoin you spend. It should be a lot of storage for very little cost if we get it right.
At the moment we have limited clients to 5Mb and vaults to 100Mb IIRC
Only tested TEST 1 a while back and was a bit slow and buggy, but this time the network reacts really fast and stable. No problems here. Wow 1 vault average only taking about 0,4% CPU on a I7 and Windows 8. Thumbs up peeps!!!
Initially creating a new account was slow but I expect that was the vault trying to catch up… terminal for the launcher complaining about finding an IGD gateway, whatever that is.
WARN 18:36:08.606655936 [w_result lib.rs:288] Failed to find an IGD gateway on network interface wlan0 192.168.1.43. igd::search_gateway_from_timeout returned an error: IO error: Resource temporarily unavailable (os error 11)
but then it’s picked up and all working well, thought the demo app is a bit slow to respond to registering names and moving to the manage websites. I’ll try data upload in a bit.
for now I’ve put up a few sites… I guess the challenge from the OP is to see if we can break the network badly enough to lose what’s put up…
I’m on windows 10, should work on 7 as well. Go to your little search screen, type:
%appdata%
You’ll see a map called Appdata/roaming. Now I click on Appdata in the address-bar. In this map choose > Local and then > Temp and search for maps called Safe Vault. You’ll have more from the old tests, so check date to see which one is from today. Thanks to @seneca for telling me where this stuff is, I didn’t had a clue ;-).
I removed some of the images because of size restrictions. Adding more images made the page load even longer. I didn’t removed the code that contains blank images because I plan to put them back in later.
@anon40790172 I never knew there was chuck listings. I wonder where it is stored in linux. Hmm.
I’m looking forward to private data being able to overwrite files… and then have options to rename files and directories. The overwrite/merge directories is the bigger pain.
Unclear how much space is available for private data… some indicator on the app would be great. I seem to be able to upload more than 5MB which I’d thought was the limit - or is that just the individual file limit??.. or is it sticking now because I’m hitting that 5MB? Will try again just uploading what I know is more rather than adding to existing.
In my mind, once maintaining data persistence is tested, live and ready, SAFE Network will be officially launched and its Long Term Support (LTS) version will be running in the wild.
In other words, when a new user creates an account with PIN, passphrase etc., it will live on and remain through subsequent tests and versions. Despite all the upcoming apps will not quite be ready, user accounts will exist, remain and can be accessed in the long run, so I’d argue THAT is the MVP.
