Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10276

Clarify mutable BSON error handling and invariant checking

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.5.2
    • None
    • Write Ops
    • None

    Description

      Mutable BSON mostly uses Status codes to return errors upstream, however there are some open questions about what to do for cases where this is not possible, or for which the error indicates a fundamental abuse of the API (e.g. calling a method on a non-OK Element, which is arguably much like dereferencing an invalid shared pointer). Currently, these fundamental cases are handled with 'verify', but this is not ideal, as verify a) can't be tested, and b) doesn't provide much context. We need to determine whether these verify calls should be masserts, dasserts, fasserts, or removed.

      Attachments

        Activity

          People

            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: