I found a way to see the server when launching the application inititally, goto terminal immediately after launching and scroll to top of terminal to see if server connected or not.
Creating a new wallet
Lightclient connecting to https://lite.nyami.org:443/
I found a way to see the server when launching the application inititally, goto terminal immediately after launching and scroll to top of terminal to see if server connected or not.
For more difficult solution, use sdl-cli.
`./target/release/silentdragonlite-cli --server https://lite.nyami.org`
```
Creating a new wallet
Lightclient connecting to https://lite.nyami.org:443/
```
I found a way to see the server when launching the application inititally, goto terminal immediately after launching and scroll to top of terminal to see if server connected or not.
Yeah, I kept having to do this while testing the SDL wallet which is why I filed this issue because a normal user is not going to be able to do that and might also want confirmation that they are connected to a specific SDL server.
> I found a way to see the server when launching the application inititally, goto terminal immediately after launching and scroll to top of terminal to see if server connected or not.
Yeah, I kept having to do this while testing the SDL wallet which is why I filed this issue because a normal user is not going to be able to do that and might also want confirmation that they are connected to a specific SDL server.
The code I am working on will show the "Current Server" as well as the "Configured Server", which is what is listed in the config file. They will be different if the configured server is down and the code automatically tried other known servers. It will also render the value of the stickyServer config option
The code I am working on will show the "Current Server" as well as the "Configured Server", which is what is listed in the config file. They will be different if the configured server is down and the code automatically tried other known servers. It will also render the value of the `stickyServer` config option
The code currently works, but I could not implement "Configured Server", only "Current Server". The internals do not keep track of a configured vs randomly chosen server, if the configured server is down, the internals choose a new server and store it in the same place as a configured server, and also sometimes writes that back out to disk.
The code currently works, but I could not implement "Configured Server", only "Current Server". The internals do not keep track of a configured vs randomly chosen server, if the configured server is down, the internals choose a new server and store it in the same place as a configured server, and also sometimes writes that back out to disk.
@jahway603 @onryo @odinzu plz test if you can, `show_server` branch
The values of "Current Server" and "Sticky Server" should be rendered, even if all other things still say "Loading..."
To test this branch:
* Start SDL
* Close syncing GUI modal, if necessary
* Switch to Hushd tab
* The values of "Current Server" and "Sticky Server" should be rendered, even if all other things still say "Loading..."
One has to go fishing in the logs to find whether the server they think they connected to had actually had a failed attempted.
I found a way to see the server when launching the application inititally, goto terminal immediately after launching and scroll to top of terminal to see if server connected or not.
For more difficult solution, use sdl-cli.
./target/release/silentdragonlite-cli --server https://lite.nyami.orgI use
clearbefore launching SDL, so then I can close it and scroll to the very top.Yeah, I kept having to do this while testing the SDL wallet which is why I filed this issue because a normal user is not going to be able to do that and might also want confirmation that they are connected to a specific SDL server.
We could show the currently-connected SDL server in the Hushd tab, which I think is the most useful for users reporting bugs.
Currently working on this on the
show_serverbranchThe code I am working on will show the "Current Server" as well as the "Configured Server", which is what is listed in the config file. They will be different if the configured server is down and the code automatically tried other known servers. It will also render the value of the
stickyServerconfig optionThe code currently works, but I could not implement "Configured Server", only "Current Server". The internals do not keep track of a configured vs randomly chosen server, if the configured server is down, the internals choose a new server and store it in the same place as a configured server, and also sometimes writes that back out to disk.
@jahway603 @onryo @odinzu plz test if you can,
show_serverbranchTo test this branch:
Um, how to switch to Hushd tab? 😧
I thought it will be somewhere in "Information about Hush". @duke
@onryo yes, its there at the bottom. That tab is called the "hushdTab" internally, like SD
Works well.
It's looking good to me when testing.
Just merged this to
dev