[129RC3] Exit command in external browser
Hello,
It's may be both bug and feature request.
If an "Exit" menu command is performed in an external browser, the GUI interface does not indicated backend is stopped/not available.
Technically external browser GUI continue working but starts reporting http request errors.
In browser console logs many errors like this "WebSocket connection to 'ws://localhost:8080/websocket/updates' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED"
It would be nice if GUI detects/expect disconnect on Exit menu command and respond correspondingly (inform user/redirect to a waiting page/retry/reload/whatever.. improvising)
Highly appreciated if that can be fixed/implemented.
Tx. Enyx
Attachments
No attachments
-
Votes 0
-
Project StrategyQuant X
-
Type Bug
-
Status Fixed
-
Priority Normal
History
Votes: 0
© Copyright. All rights reserved. ProjectPanel.com
For completeness adding CodeEditor and Debug console too.
Indeed there is something weird there. If SQX "Exit" is selected, Code editor keeps working/communicating with backend. It starts to return errors only if sqcli -exit is executed.