Couchbase nodejs error code mapping

alexegli · July 20, 2015, 2:25pm

Using couchbase nodejs (v2.0.6) when running views the errors I got back were still encoded, they just said 1, or 6. I can’t tell which function they’re coming from or if they correspond to a constant in the errors.js file in the couchbase nodejs library, or if they are coming straight from the couchbase server. Does anyone know how I can map these integer values to actual errors?

matthew · July 22, 2015, 1:03pm

hey @brett19 do we have a table of error code numbers and their corresponding description?

brett19 · July 22, 2015, 5:29pm

Hey matthew,

The best thing we have is found here:

github.com

couchbase/libcouchbase/blob/master/include/libcouchbase/error.h#L97




/* PRIVATE. This is just here to instruct/inform users to use the more detailed codes */
#define LCB__ERR_USEDETAILS \
   "Enable detailed error codes (via LCB_CNTL_DETAILED_ERRCODES, or via " \
   "`detailed_errcodes` in the connection string) and/or enable logging to " \
   "get more information"


/**
* @brief XMacro for all error types
* @param X macro to be invoked for each function. This will accept the following
* arguments:
*  - Raw unquoted literal error identifier (e.g. `LCB_EINVAL`)
*  - Code for the error (e.g. `0x23`)
*  - Set of categories for the specific error (e.g. `LCB_ERRTYPE_FOO|LCB_ERRTYPE_BAR`)
*  - Quoted string literal describing the error (e.g. `"This is sad"`)
*/
#define LCB_XERR(X) \
   /** Success */ \
   X(LCB_SUCCESS, 0x00, 0, "Success (Not an error)") \
   \
   X(LCB_AUTH_CONTINUE, 0x01, LCB_ERRTYPE_INTERNAL|LCB_ERRTYPE_FATAL|LCB_ERRTYPE_SRVGEN, \

Cheers, Brett