-
Notifications
You must be signed in to change notification settings - Fork 887
feat(site): add workspace health badge to workspace list #8387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
> = ({ workspace, className }) => { | ||
return ( | ||
<Maybe | ||
condition={["starting", "running", "stopping"].includes( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review: Should we modify the API endpoint instead and do this on the API so that workspace.health = null
when it's not possible to know (e.g. stopped workspace)?
icon={workspace.health.healthy ? <FavoriteIcon /> : <ErrorIcon />} | ||
text={workspace.health.healthy ? "Healthy" : "Unhealthy"} | ||
type={workspace.health.healthy ? "success" : "warning"} | ||
/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use the popover component here when healthy = false?
When can a workspace be Running but not healthy? What does it mean? |
It can mean different things, for instance:
One option here is to eliminate the extra column, and replace |
As far as I understand, In 3rd case, we can have an unhealthy workspace that still has a valuable process running, and restarting would make the user lose any progress. We should allow reconnecting to such workspaces. |
Fixes #6461
Todo:
This PR introduces the following UI change: