1) Remote access started with sqcli -gui
2) SQX accessed remotely (supported Chrome, FF does not work)
3) Started three concurrent jobs using remote browser (Vanilla SQX install, provided samples used only)
- Data manager data update (3.1)
- Builder task (3.2)
- A Custom Project build (3.3)
4) Remote browser closed, SQX backed keeps running started tasks
5) SQX accessed again remotely via browser (a new session)
6) At this moment remote browser GUI shows (see attachment)
- Ongoing Data manager data update - (is OK)
- Builder task - No running status shown
- A Custom Project build - No running status shown
7) Click on BuilderĀ -> GUI start correctly reflecting running status (is OK now)
8) Click on Cusom Project BuildĀ -> GUI start correctly reflecting running status after some time (and is OK now)
Tx. Enyx
A side comment:
Remote GUI is an awesome feature. Anyway build-in GUI uses same underlying technology and methodology. Good job!
On the other side, important work happens on the back-end crunching the strategies all day long. There are number of issues being reported routinely about internal GUI causing SQX to stop/slowdown. I have seen/experienced many of these as well. Usually It's currently not fully possible to "resume" a stopped job (depends on many factors) which does bring some level of frustration if internal GUI breaks.
Polishing remote GUI would allow to improved situation and introduce some additional flexibility in the product.
Tx. Enyx