Use Case

Flakey test: Client Side Encryption Prose Corpus Test should pass corpus without client schema

MongoCryptError: KMS request closed
   at onclose (src/client-side-encryption/state_machine.ts:58:49)
   at TLSSocket.<anonymous> (src/client-side-encryption/state_machine.ts:59:77)
   at Object.onceWrapper (node:events:628:26)
   at TLSSocket.emit (node:events:525:35)
   at TLSSocket.emit (node:domain:489:12)
   at node:net:301:12
   at TCP.done (node:_tls_wrap:588:7)

User Experience

• None

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

• skip or fix

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