Wait half-naked
2 Likes
We are co-ordinating with NEMTus just now to see when their scheduling works now that they know when the release is available. Once we know we will update, it is likely to be something like NEMTus early-mid next week, then NGL stress tests afterwards - mid-end of the week, or early the week following. These are very approximate until we finish co-ordinating though. I will confirm more when we have the info.
2 Likes
The default node of the desktop wallet is the node before Reset.
I want to select a node, but it shows up as an invalid node and cannot work.
Please update the NGL node or let me know if there is another workaround.
There is no CLI right now, so you have to use the SDK…
3 Likes
A lot of nodes are running on older versions(v0.10.0).
Could you please review them as soon as possible.
3 Likes
Now , It looks like most of the nodes are running on 0.10.0.5.
However, if I check in /node/server by REST API, I can see the following
{“serverInfo”:{“restVersion”:“2.2.2”,“sdkVersion”:“2.2.2”}}
The current latest version is 2.3.0, so symbol-sdk-0.23.0 does not work.
Are you sure they are v.0.10.0.5?
1 Like
Hi @GodTanu thanks, just catching up, there was an issue with the release build that for some reason didn’t pick up those change, it will be fixed today:
2 Likes
Checking the website: https://symbolnodes.org/nodes_testnet they look to be mostly updated now (exception of some community ones as to be expected). I suspect it may have taken a moment to update
Can you give me one of the links that says 2.2.2 please? The ones I checked at random look like below:
{“serverInfo”:{“restVersion”:“2.3.0”,“sdkVersion”:“2.3.0”}}
That is from:
- http://api-01.ap-northeast-1.testnet.symboldev.network:3000/node/server
- http://api-01.ap-southeast-1.testnet.symboldev.network:3000/node/server
- http://api-01.eu-central-1.testnet.symboldev.network:3000/node/server
- http://api-01.us-east-1.testnet.symboldev.network:3000/node/server
- http://api-01.eu-west-1.testnet.symboldev.network:3000/node/server
- http://api-01.us-west-1.testnet.symboldev.network:3000/node/server
It may just have taken some time for caches to clear etc somewhere or you may be looking at another node(s) I haven’t checked manually, just want to validate
EDIT:
I saw a conversation on Public slack after posting this, looks like the rolling upgrades took a little while to go through and some of the NGL nodes needed to be upgraded with the release from last night: https://nem2.slack.com/archives/C9E7N7H1N/p1610711520026900?thread_ts=1610692103.024500&cid=C9E7N7H1N
Should now be fixed on the core nodes, the others will be updated shortly
1 Like
I’ve tried a lot of things, and I’ve learned something.
Node synchronization time is long (took 8 hours)
The quality of the desktop wallet is poor.
-The screen display is not real time.
-There are problems such as frequent timeouts.
-Unable to set fees (always times out if other than recommended).
-“Invalid node” is displayed when changing nodes.
In other words, the operation is unstable.
I changed the connection of my desktop wallet to my node. It showed “invalid node” several times, but after many iterations I was able to change it.
Then I had to recreate the profile.
Many of the same problems occur when the default node is not changed. I would like to see this response given a higher priority.
1 Like
Thanks @GodTanu:
Synchronisation, yes this is taking longer than it did yesterday. It is due to the number of nodes synchronising and amount of data. We are monitoring it and once the nodes all come online will rerun the synchronisations to make sure it was just a settling in problem, or not.
Desktop wallet, is struggling a little bit because of the network load while the synchronisations are happening some of the nodes are working more slowly due to the load.
I would stop testing the Wallet until the new build is released. We know the build has problems and will be frustrating. The new build is likely to be ready and tested in a few hours so should be there by the time you wake up.
3 Likes
Better check it out before releasing it.
If you are a professional.
3 Likes
Further to my reply above. An update is available on the main release thread:
On the wallet specifically:
The quality of the desktop wallet is poor.
-The screen display is not real time.
-There are problems such as frequent timeouts.
-Unable to set fees (always times out if other than recommended).
The first two issues in appear to be linked to this issue reported by Xembook which were not occurring during our testing and have only appeared since public release.
The last issue is a build issue and has been resolved.
We have taken the decision to not release the wallet build today. The timeouts/notifications etc lead to a poor user experience of the wallet and the problem is probably not the wallet directly given xembook is seeing similar without the wallet. Investigation into the underlying problem will take some more time and I will update as soon as possible.
I know this is disappointing but do not want to create further frustration or lost time by releasing it when we know it will show similar user experience as your workaround one.
I will update as soon as more information is known and want to assure people that this issue was not present in testing over the past 1 - 1.5 weeks it has shown as the network has had public nodes and upgrades applied.
I assume no NEMTus testing will happen till the wallet is out? And we again in a point where there is no information about how long can this issue resolving take time?
I will provide instructions on how to reproduce.
3 Likes
Thankyou this is very helpful.
We think the issue has been found and are testing it over the weekend. I will ask the team to use these steps to check it resolves this issue as well.
3 Likes
Correct on Nemtus testing.
The issue has been found and a resolution is in testing before releasing the fixes. At this stage I would estimate Mon/Tue for the patch
3 Likes
Thanks for the heads up. Wishing an easy work for the team on this one.
2 Likes
why it takes so slow?
Finalization is currently delayed.
I predict that there is some problem with the public testnet.
Please let me know if you have any information.
4 Likes
@DaveH can you please answer if there is another issue at the testnet now so the community isnt again the last who will find it out.