)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36725,"name":"Nilesh Thathagar","display_name":"Nilesh Thathagar","email":"nilesh.thathagar@dell.com","username":"NileshT"},"change_message_id":"90f55b54685fc778b028c7be2e3b04681f8a508e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"383f4efb_be1eaa55","updated":"2026-05-15 10:35:41.000000000","message":"Brian\u0027s comment\n\n``Before returning from this function, you could additionally verify that a non-OK response does in fact have an errorCode, and if it doesn\u0027t, you could raise a VolumeBackendAPIException right here. You seem to be making an assumption that the driver will always be talking directly to the SAN via the REST API, but it\u0027s possible that there could be something else in the path (for example, a rate limiter) that could return a non-OK response code and that won\u0027t contain the errorCode from the SAN\u0027s REST API.``\n\nreply: Currently, most functions log messages based on the HTTP status. If we add an errorCode check in the response message, it will impact these functions. Therefore, for now, we are removing the errorCode checkmark from the new NVMe REST functions.","commit_id":"b7c09ac13949dddbc7bfc4a9aaee71119d2d7de5"}]}