Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-4393

Let connecting not be blocking

    • Type: Icon: Story Story
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 1.26.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Not Needed
    • Iteration Tangerine, Iteration Uglifruit, Iteration Vegetable

      It looks like there are cases where connecting to a connection can get into an unexpected state: https://jira.mongodb.org/browse/COMPASS-4219 

      In these cases, where the connection is still occurring after the connection's timeout has elapsed, we can cancel the request, show a connection error, and free up the UI so that the user isn't blocked. We've done something a bit similar with VSCode: https://jira.mongodb.org/browse/VSCODE-155 
      It would also be good to know what's causing the actual issue in the https://jira.mongodb.org/browse/COMPASS-4219 ticket, so lets look around a bit. This ticket is more for ensuring the user's experience is never interrupted from a stalled state.

      This ticket should also take into consideration specific timeouts the user may have added to the connection (we don't want to unblock/cancel the connection request if there is a manually added really long timeout on the connection). 

            Assignee:
            rhys.howell@mongodb.com Rhys Howell
            Reporter:
            rhys.howell@mongodb.com Rhys Howell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: