Dashboard: starting and stopping a workspace doesn't update UI
See original GitHub issueDescription
Starting or stopping a workspace from Workspaces
view doesn’t update workspace’s status. Refreshing the page fixes the problem.
Reproduction Steps
- start latest version backend and frontend
- create a workspace
- open
Workspaces
view - stop the workspace
- start the workspace
OS and version:
Fedora 29
Diagnostics:
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Troubleshoot a WorkSpace stuck in starting, rebooting, or ...
My Amazon WorkSpaces Windows WorkSpace is stuck in the starting, rebooting, or stopping status. Why is this happening, and how can I fix...
Read more >Google Workspace Known Issues
What's not a Known Issue. Product outages: Up-to-date outage information is posted within the Google Workspace Status Dashboard. Feature Ideas: We'd love ...
Read more >Set up custom UI actions in Workspace
Set up UI actions to customize Workspace for your organization. UI actions include custom buttons, menu items and limiting access to forms based...
Read more >Create a workspace - Power BI | Microsoft Learn
Learn how to create a workspace: a collection of dashboards, reports, and paginated reports built to deliver key metrics for your ...
Read more >Update | Citrix Workspace app for Windows
Starting with Version 2105, Citrix Workspace Updates log paths are modified. The Workspace Updates logs are present at C:\Program Files ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ppitonak Command needs to be a single comment
Seems this issue was actual only for running local Che with docker. @ppitonak feel free to reopen it if you still face the same behavior on the latest Che