yep, as long as the first is still sitting there with the version info up during initialisation the second vault starts ok, as soon as it kicks of the second will dip out…
rup
New account + Demo App Authorisation failed… after spawning two instances… which I took to be a good sign that it’s retrying. However, the first appeared to fail with the terminal detail below:
DEBUG 19:56:10.30 - Authorised request :://auth
DEBUG 19:56:10.36 - Decrypted session id :: undefined
WARN 19:56:10.39 - Session ID not found
ERROR 19:56:39.570334848 [safe_core::ffi mod.rs:242]
--------------------------------------------------
| FfiError::NfsError -> NfsError::CoreError -> Invalid data successor - CoreError::MutationFailure::{ reason: InvalidSuccessor, data_id: Structured(8da42c.., 15101) }
--------------------------------------------------
ERROR 19:56:39.583 - FFI/mod/auth.js - Getting App Root Dir Key failed with code -25
What I saw:
I don’t know if that’s simply because network is loaded and not falling back to basics like authorising apps.
2 Likes
Trying to Authorise Demo App again, sees an odd situation, that the launcher suggests in Account [Authorised Apps] Maidsafe Demo App : Status Unknown
Yet, in the Logs it suggests Anonymous App Status Success
But the Demo App itself is still waiting for authorisation.
So, some confusion there of message not received by Demo App if it has been successful… and if it has been successful, I wonder, that it hasn’t retried in a way that the launcher replies with surprise that it’s already authorised why you ask…
Trivial typo: Error on trying to create an existing account is “Invalid Key/Pin/Password”, instead of “Account exists”
4 Likes
There definitely will be a problem 
even if you manage to start vaults at the same time and beacon hasn’t detected the other vault, they’ll still use the same chunk store in disk so basically overwrite and corrupt chunks from both instances. So end up with both vaults actually not serving any data at the end.
It is a valid issue tho and something to address in code to not end up in this situation.
5 Likes
I’m able to upload private files up to 1MB. Seems everything above that gives trouble at the moment.
4 Likes
they are on different machines within the same data centre… even though on total different subnets… i’m not silly enough to run 2 on the same box!! 
lol…
rup
3 Likes
Not convinced it’s about file size, though big files perhaps have more traffic… I’m stuck on 31% now for upload of directory with [26 items, totalling 158.5 kB]
Great work team on releasing the redesigned launcher this quick. I had a little lag while authorising the demo app and worked on my 3rd try, other than that everything works as expected. Can’t even notice the CPU load.
5 Likes
single 44mb mov file took 15 mins but got there in the end…
rup
3 Likes
Can’t wait to jump right in. Thank you team for putting it out in great time!
4 Likes
Private data uploading fine: 1mb, 3mb and 11mb. Trying 20mb+ now.
2 Likes
unforgettable… hopefully.
2 Likes
Naive question: why in this version only a password is required to log in? No keyword, no PIN? Or were they stored somewhere from the previous version?
No, complete new network. I think they wanted to try different user experience.
2 Likes
User credentials merged to a single input
Sorry didn’t read this. So is this just an experiment, or finalized?
I’m positively surprised by the new launcher GUI. Very nice to be able to follow the PUTs and GETs in a time graph.
My vault has been running for two hours and has received a few hundred PUT operations thus far. Everything seems to be running smoothly.
The demo app has a small GUI issue where it gets stuck uploading a new file at 99% on the progress bar, even though the launcher log shows the file creation was successful. Closing and re-opening the demo app shows the file in my private area and I’m able to download and open it, so it really is just a GUI issue.
5 Likes
115 x 3k text files around 5 mins, quick quick…
rup
2 Likes
Very cool launcher UI.
Overall speed seems to be good.
few things i noticed:
- upload a file with the same name gives an undefined error
- upload progress bar seams to be broken (stuick @ 99%)
- not possible to navigate safenet while uload is stuck ?
2 Likes
Some strange behavior / errors:
1.) Uploaded ~7 MB file (private folder): first stuck at 99% but finished after some minutes
2.) Closed demo app & launcher
3.) Restarted launcher & demo app: file still there!
4.) Uploaded ~37 MB file (private folder): stuck at 99% and won’t finish (maybe it would have needed more than 10 min.)
5.) Forced upload cancellation by closing the demo app: launcher changes event from IN PROGRESS to SUCCESS??
6.) Restarted demo app: “Fetch Directory FAILURE” → empty file list … tried several times (see screenshot below)
7.) Several restarts didn’t help → my account / private folder seems broken (uploads are also not possible anymore).
Minor issue: The top most event at “21:17:16” stays on top (not ordered descending correctly)
Usability feedback:
For end users (especially not-so-tech-savvy ones) it might seem strange to register with only a password (which also acts as identification). Would consider to require at least a username + pw and generate all needed parts from these values (although ofc technically not required)
Upload not working anymore:
4 Likes