[SERVER-33909] Provide more detailed error reporting from CAPI Created: 15/Mar/18  Updated: 29/Oct/23  Resolved: 03/May/18

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: ADAM Martin (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-33426 lib mongod CAPI necessary debugging i... Closed
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2018-03-26, Platforms 2018-04-09, Platforms 2018-04-23, Platforms 2018-05-07
Participants:

 Description   

Errors that are surfaced to the user via typical uassert or related channels will be handled correctly, but unexpected errors currently surface only an indication of failure, with no additional diagnostic info. We should provide a way to obtain that information from CAPI.



 Comments   
Comment by Githook User [ 03/May/18 ]

Author:

{'email': 'adam.martin@10gen.com', 'name': 'ADAM David Alan Martin', 'username': 'adamlsd'}

Message: SERVER-33909 More detailed error reporting from CAPI

The `libmongodbcapi.h` file now contains detailed documentation of
all preconditions, postconditions, and behaviors. All operations
now take a `libmongodbcapi_status *` argument which will be
populated with the failure results of an operation.

The internals of how the `libmongodbcapi_` functions are implemented
have been rewritten to catch and report nearly all failures, as well
as to use more native C++ idioms such as exceptions and RAII.
Branch: master
https://github.com/mongodb/mongo/commit/6b23bd026bb74b1e44d93951662070076e99b361

Generated at Thu Feb 08 04:34:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.