GetFailed event does not always return correct reason

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.5.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If the connection pool is empty and the connect call on the newly created connection fails, we publish a GetFailed CMAP event. This event's Reason field should be set to ReasonConnectionErrored.

      Incorrect event construction is at https://github.com/mongodb/mongo-go-driver/blob/a62c7d7c704d9269a5399f80e266fdefb4f5da39/x/mongo/driver/topology/pool.go#L443.

            Assignee:
            Divjot Arora (Inactive)
            Reporter:
            Divjot Arora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: