Thank you again, for all the recent help with these tests, it may seem like a pain, but it is vital we do these tests in this manner. We are closing in on more formal releases in the near future. It’s been a pretty frantic day today, but worth it. Viv and the team really made best use of every second in getting many commits merged and these releases done. Appveyor (Windows continous integration) has really caused us a lot of pain in waiting, we must resolve that issue soon.
This test will be likely very destructive, or at least should be. We have been already surprised by robustness of the network, that is what the tests are for though. So let’s find out…
TEST 5 will now commence and with the usual help and binaries, we hope you can help by running a (singular 
) vault and / or create some temporary sites,etc. We do not expect this test to last long at all. This is destined to destroy the network (we imagine) to provide us the information we need. This network is very unlikely to last long as we have disabled potential network saving features in an effort to provide the data we need to further enhance message priorities and some other smaller features.
This test is, however, expected to show improved data handling, speed and reduce network usage (again). We are still working on two main issues:
- Data persistence between networks
- Handling of nodes that have insufficient capabilities, although we are reducing the requirement for all nodes quite a bit through these tests.
###Launcher limitation
The current launcher, whilst improved is not the new UX yet. There is a bug being worked on where this does require to be restarted every few minutes. It is a pain, but we did not want to slow the network test due to this one. Please bear with us and we will release a fix over the next few days to remedy this issue.
So feel free to flood the network with data, sites, etc. but also realise this will be temporary and extremely valuable to us. We may restart with a new launcher if necessary, but hopefully we will just provide a new launcher if the network is stable enough for that.
###Get involved in TEST 5!
Please be aware this release will not allow older nodes or clients to connect to the network. You must use the new binaries below to connect to the TEST 5 network.
For this test you can run only 1 Vault node per LAN - running more than 1 will result in this message More than 1 routing node found on LAN. Currently this is not supported - for the objectives of this test please respect this restriction.
chunk_store_path can now be configured and this can be set within the vault config file > safe_vault.vault.config.
This is a test network and comes with the normal risks of using pre-release software. Please also be aware that this test network and will be reset, wiping all data that is stored on it.
SAFE Vault binaries
[SAFE Launcher binaries]
(Release SAFE Launcher v0.5.1 · maidsafe-archive/safe_launcher · GitHub)
SAFE Demonstration Application binaries
How to download and install SAFE Launcher
Using SAFE Launcher
How to download and install the SAFE Demo App
Using the SAFE Demo App
###Where should I report issues?
GitHub is the best place to report issues and bugs. Using GitHub will help us (MaidSafe) manage issues and prioritise work within the Dev team faster.
For SAFE Vault issues / bugs
For SAFE Launcher issues / bugs
For SAFE Demonstration Application issues / bugs
If you are not sure if it is a real bug and have a question, the forums #support category is a great place to post this. As we know this is a friendly and responsive community and someone will help you out and of course as always thank you for participating in TEST 5.
