Skip to content

Initial coordination dial in Coder Desktop should fail fast #18599

@ethanndickson

Description

@ethanndickson

Currently, the first time Coder Desktop dials /api/v2/tailnet is within the main Controller.Run loop:

tailnetClients, err := c.Dialer.Dial(c.ctx, c.ResumeTokenCtrl)

This means the tunnel sends the StartResponse with success set to true without knowing whether or not it was able to dial the coordination endpoint. This results in a poor UX if we're not able to dial it initially; Coder Connect appears functional but is not - the only sign something went wrong is the No workspaces message, and N error logs, for each retry attempt.

Instead, we should fail fast, and send a StartResponse with success set to false if we fail to dial right after starting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy