Use OvertCommandListener wherever sensitive events are not needed

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Python Drivers
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      We currently use EventListener in many test suites, even when we do not rely on sensitive events for testing. This causes failures after PYTHON-4528, which made each test use its own client. Previously, a single client would be shared across one test suite, so any sensitive auth events would already have occurred before the test ran.

              Assignee:
              Noah Stapp
              Reporter:
              Noah Stapp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: