You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decrediton and bruig let you view the logs from the UI - will make troubleshooting and supporting less savy users easier if it can be viewed directly from the UI.
The text was updated successfully, but these errors were encountered:
I have spent a couple of days looking into this and do not think it is such a good plan for bison wallet.
Bruig & Decrediton have access to the filesystem (fs) and can open and tail the log file in some way. Their UI's are not sand-boxed. While bisonw web server also has access to the fs the bison wallet client Gui code runs in a browser and has no access to the fs and cannot open or manipulate files - only "download" them (from the user's system to the default Download folder on the same system) - so just find the log file for the user using this and put it where they know where to look for it.
The test code is much more complicated:
In the web server (bisonw) it has to capture each log line after it has been emitted anywhere in the bisonw code. Each log line then has to be sent to the browser over a web-socket as a notification. That is then captured in the browser code and stored in a buffer for when the user wants to look at a live logging page. That is a lot of log lines being sent over tcpip to web client lowering the bandwidth for other more important messages about orders, mm, bonds, swaps, etc.
I can put up the testing branch on my fork for a short time if anyone is interested.
We could also look at a simple "download log file" dialog to help with debugging issues .. probably a link in the hamburger menu.
Decrediton and bruig let you view the logs from the UI - will make troubleshooting and supporting less savy users easier if it can be viewed directly from the UI.
The text was updated successfully, but these errors were encountered: