Use Case

Flaky test: CSOT State machine #markCommand when csot is enabled and markCommand() takes longer than the remaining timeoutMS the command should fail due to a timeout error

AssertionError: expected Buffer[ 17, 0, 0, 0, 1, 111, 107, 0, 0, 0, 0, 0, 0, 0, 240, 63, 0 ] to be an instance of MongoOperationTimeoutError
 at Context.<anonymous> (test/integration/client-side-encryption/driver.test.ts:851:33)
 at processTicksAndRejections (node:internal/process/task_queues:95:5)

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward