grep suggests none of the log files in /safe_launcher/ now have that message. However, I wasn’t being careful and started up another account - restarting the launcher; so, I wonder then the logs have been refreshed. I can’t see the error logged either.
If logs are refreshed each new session, perhaps we backup logs where new errors occur.
and just for completeness, I went back in now and retried the upload and it worked fine. The previous had left a 0 byte file, so I just deleted it and retried the upload. Clearly then just a connection issue but a clean one.
Thank you very much! The main things we are able to work on at this point in the SAFE Network’s development are the UI and organization, so a lot of work has gone into making our brand image etc.
We wanted something unique to us and independent from MaidSafe etc as our brand should be, and have made many layouts and images for this, and have somewhat gravitated towards those that depict our company’s roots in San Francisco.
However we are still finishing some of the other designs and will release them very shortly, and most likely have an ASDGC vote to decide
Sorry, there was an issue with the tcp mapper servers(not the actual vaults) and we needed to restart them. Data stored in the network is intact. However we do need to update launchers config file without which we will be getting stuck when started with “Trying to connect” in launchers UI.
For those of you who wish to make the update by editing the launcher’s crust.config file manually, we’ll need to change:
Linux and Win: safe_launcher.crust.config file next to the launcher binary.
OSX (bit tricky): safe_launcher Helper.crust.config file which will be inside the launcher app package: safe_launcher.app/Contents/Frameworks/safe_launcher Helper.app/Contents/MacOS
That should get us bootstrapped fine to the network again. Sorry about this issue. It’s going to be another thing thats removed with the mio version of crust as we wouldn’t need such endpoints anymore in the config file
Sorry I didn’t this comment till now! I don’t think it’s really objections so much as a general skepticism about the project—basically, whether or not it will work. Though I think this is mainly coming from people looking at the charts as opposed to the dev updates.
Is this network down? This is the first time we have had an issue connecting to it.
Was supposed to be our go-to, reliable network for development
I know the other networks were recently taken down, and we’re waiting for a new one to begin, but now this Stable Droplet Test net is also down, correct?
