• Type: Icon: Sub-task Sub-task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a... Node.js engineer
      I want... reliably run a single command
      So that... my expectations about a CSOT timeout are consistent

      While working on testing the maxTimeMS change for commands there is an inconsistency where the tests don't reflect reality leading to inconsistent timeouts. The tests connect a MongoClient with an internal setting that skips the initial ping, in practice this behavior isn't the same for folks who've set a timeoutMS option in their URI (as the tests do) and call connect.

      User Impact

      • None

      Dependencies

      • Execute operation loop refactor merged to main

      Unknowns

      • None

      Acceptance Criteria

      Implementation Requirements

      • Move topology.connect() logic into selectServer() when the topology hasn't been initialized yet.
      • Move ping when credentials exist step into client.connect()
      • Remove auto-connect logic from execute operation
      • Remove connect from unified test runner

      Testing Requirements

      • Existing tests

      Documentation Requirements

      • None

      Follow Up Requirements

      • None

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: