Investigate CSFLE async cryptoCallbacks throwing synchronously

XMLWordPrintableJSON

    • Not Needed
    • None
    • 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

      On latest, failures have developed on the tests that run only when there's a server to test against:

       1) cryptoCallbacks
      error testing
        should error with a specific kms error when hmacSha256Hook fails:
    AssertionError: expected [Function] to throw an error
     at Context.<anonymous> (test/cryptoCallbacks.test.js:213:96)
     at processImmediate (internal/timers.js:461:21)
2) cryptoCallbacks
      error testing
        should error with a specific kms error when sha256Hook fails:
    AssertionError: expected [Function] to throw an error
     at Context.<anonymous> (test/cryptoCallbacks.test.js:213:96)
     at processImmediate (internal/timers.js:461:21)

      As of March 9 2022, the failures have been fixed, but there's the question of why are callback based APIs throwing synchronously. We should take a look and see if it's reasonable to change or document it for a major version fix.

            Assignee:
            Unassigned
            Reporter:
            Neal Beeken
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: