Skip to content

Final output on workspace creation shows "connecting" forever - confusing UX #1036

Closed

Description

@f0ssel
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".

Activity

  1. changed the title [-]Bug: [/-] [+]Bug: final output on workspace creation shows "connecting" forever - confusing UX[/+] on Apr 15, 2022
  2. added this to the V2 Beta milestone on May 4, 2022
  3. misskniss commented on May 5, 2022

    @misskniss

    @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?

  4. misskniss commented on May 5, 2022

    @misskniss

    @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.

  5. removed this from the V2 Beta milestone on May 5, 2022
  6. 16 remaining items

  7. removed their assignment
    on May 20, 2022
  8. f0ssel commented on May 20, 2022

    @f0ssel
    MemberAuthor

    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.

  9. mafredri commented on May 24, 2022

    @mafredri
    Member

    @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?

  10. self-assigned this
    on May 31, 2022
  11. spikecurtis commented on May 31, 2022

    @spikecurtis
    Collaborator

    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.

  12. 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
  13. self-assigned this
    on Jun 8, 2022
  14. added a commit that references this issue on Jun 8, 2022
    23e5659
  15. added a commit that references this issue on Jun 9, 2022
    2621093
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

apiArea: HTTP APIdocsArea: coder.com/docs

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions