- Notifications
You must be signed in to change notification settings - Fork928
fix: hiding agent status on stopped workspaces#3512
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| error = "Error", | ||
| loading = "Loading", | ||
| } | ||
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.
I moved this out of a component directory and into our util file so we can have properly typed statuses.
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.
Looks good to me! Sorry for the slow review!
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Joe Previte <jjprevite@gmail.com>
Uh oh!
There was an error while loading.Please reload this page.
resolves#3484
We have an issue where workspace agent statuses are 'connecting' after a workspace has stopped. After chatting with@bpmct, we have decided to hide the agent status on stopped workspaces. We have also created tickets to address the agent status on the BE (see#3510 and#3511). This PR addresses hiding the status in the UI, only.
Before
After