Open mmulholl opened 5 years ago
The running status in the IDEs reflects the status that PFE reports via the web socket. If the status in the IDEs is going from starting to running to stopped and back to running, it's because that's the sequence of the change events coming from PFE.
Any plans to address this? Can we add some intelligence to Codewind to handle the situation?
Codewind version: 0.4.0 OS: Mac
Che version: IDE extension version: IDE version: Eclipse Kubernetes cluster:
Description:
After an Open Liberty project hits running, if you open the application view you see the Liberty Server page, if you wait for running to go to stopped and then running again you get the project page. The project should only be shown as running once the project is ready.
This is similar to : https://github.com/eclipse/codewind/issues/510
Automation makes the problem worse because we open the view as soon as we see the project status as running.
Also this appears to be a regression from 0.3.0.
Steps to reproduce:
Workaround: