Update from MaidSafe HQ
Yesterday we reproduced a “hanging” issue again, so the “fix” on Friday may have resolved something, but this proved that there was still something else at large.
Through investigations last week we also merged a fix for a potential cache dead-lock/hang here, which has probably been causing intermittent hanging in some scenarios.
Today we have also found and fixed here, another bug which has been causing hanging - this switch to
write to make this single threaded has certainly resolved a load of issues being caused by nodes not being in sync. A follow up PR going through peer review here to fix concurrency should improve this further.
So is that all hangs resolved?
Well we are not 100% sure! Only testing will confirm. However, we suspect there is still an underlying issue lurking somewhere in
qp2p which has also been causing hangs. We think the fixes and changes made over the last few days should have made things more reliable.
We’re testing these latest changes in-house now and if we feel it is reliable enough then we would push for a v6 testnet release (probably tomorrow at the earliest).
We’ve also been working in parallel to only accept nodes as Adults if they are reachable, which is in the final stages of development, so v6 will now wait for this to be added. Again, we feel this will make the network much more stable.