You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Final output on workspace creation shows "connecting" forever - confusing UX #1036
der-developer-f0ssel]
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
Outputs: 0
✔ Starting workspace [30901ms]
✔ Cleaning Up [0ms]
┌────────────────────────────────────────────────────────────────────┐
│ RESOURCE STATUS ACCESS │
├────────────────────────────────────────────────────────────────────┤
│ google_compute_disk.root ephemeral │
├────────────────────────────────────────────────────────────────────┤
│ google_compute_instance.dev ephemeral │
│ └─ dev (linux, amd64) ⦾ connecting [0s] coder ssh f0ssel │
└────────────────────────────────────────────────────────────────────┘
The f0ssel workspace has been created!
We should probably make it clear that we aren't waiting here, since it seems like the CLI is going to wait for the "connecting" to change to "connected".
I'm in favor of dropping it, @kylecarbs made the original flow so he may have thoughts, but since he's on PTO I don't think we need to wait for his input since he can give input / reimplement correctly later.
@f0ssel So we'd be dropping / not showing the resource view after creation? What about the preview, there's a mis-match of information between the two -- which is the source of truth and do we know the persistent/ephemeral status before creation is complete, and do we need to show it?
I think what's happening with the resources state being inconsistent is a bug, but it's a different bug than what's being tracked in this issue, so I'll raise a new issue to track: #1937
Let's concentrate on this issue with the "connecting" UX, and I think the best plan is still to just drop the second round of showing the resources on coder create.
changed the title [-]Bug: final output on workspace creation shows "connecting" forever - confusing UX[/-][+]Final output on workspace creation shows "connecting" forever - confusing UX[/+]on Jun 7, 2022
Activity
[-]Bug: [/-][+]Bug: final output on workspace creation shows "connecting" forever - confusing UX[/+]misskniss commentedon May 5, 2022
@tjcran We have already done grooming for this sprint (last sprint of Beta) is this an intentional injection or can this move to Community MVP?
misskniss commentedon May 5, 2022
@kylecarbs I added you to poker planning for this but there may be others you want to add. I am just assuming that this fix will be you.
16 remaining items
f0ssel commentedon May 20, 2022
I'm in favor of dropping it, @kylecarbs made the original flow so he may have thoughts, but since he's on PTO I don't think we need to wait for his input since he can give input / reimplement correctly later.
mafredri commentedon May 24, 2022
@f0ssel So we'd be dropping / not showing the resource view after creation? What about the preview, there's a mis-match of information between the two -- which is the source of truth and do we know the persistent/ephemeral status before creation is complete, and do we need to show it?
Do you have any thoughts on this @kylecarbs?
spikecurtis commentedon May 31, 2022
I think what's happening with the resources state being inconsistent is a bug, but it's a different bug than what's being tracked in this issue, so I'll raise a new issue to track: #1937
Let's concentrate on this issue with the "connecting" UX, and I think the best plan is still to just drop the second round of showing the resources on
coder create.[-]Bug: final output on workspace creation shows "connecting" forever - confusing UX[/-][+]Final output on workspace creation shows "connecting" forever - confusing UX[/+]fix: Stop showing resources after `coder create`
fix: Stop showing resources after `coder create` (#2155)