Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-4996

maybeCallback rejects with an unhandledRejection instead of uncaught exceptions

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.0, 5.0.0
    • Component/s: Error
    • Not Needed
    • 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?

      If the callback provided to `maybeCallback` throws, the process will crash with an unhandled promise rejection.  This is a behavior change from `maybePromise`, which would crash the process with an uncaught exception.

      In both cases, it is impossible for the user to recover but we continue to throw exceptions outside the async context of the promise used inside `maybeCallback`.

       

      This change applies to 

      • the legacy driver maybeCallback
      • driver v4 maybeCallback

            Assignee:
            Unassigned Unassigned
            Reporter:
            bailey.pearson@mongodb.com Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: