Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6804 Add a test to prevent unhandled rejections from passing tests
  3. NODE-6848

Flaky: Client Bulk Write CSOT enabled acknowledged writes the timeout is reached while iterating the result cursor the bulk write operation times out

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 6.15.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Not Needed

      Use Case

      Fix flakey test: Client Bulk Write CSOT enabled acknowledged writes the timeout is reached while iterating the result cursor the bulk write operation times out

            AssertionError: expected 1499 to be within 1500..2300
             at Context.<anonymous> (test/integration/crud/client_bulk_write.test.ts:307:39)
             at runMicrotasks (<anonymous>)
             at processTicksAndRejections (node:internal/process/task_queues:96: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

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

              Created:
              Updated:
              Resolved: