You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am able to show that as-promise.js has a silent failure mode where the body of the request that results in an error is not displayed to the user.
This is not the right place to solve this problem, but I could prove the body was not being reflected to the user by modifying this,
constparseBody=(body,responseType,encoding)=>{if(responseType==='json'){returnbody.length===0 ? '' : JSON.parse(body.toString());}if(responseType==='buffer'){returnBuffer.from(body);}if(responseType==='text'){returnbody.toString(encoding);}thrownewTypeError(`Unknown body type '${responseType}'`);};
This gave me much needed contextual information about
[12:29:11 PM] [semantic-release] › ✖ An error occurred while running semantic-release: HTTPError: Response code 400 (Bad Request)
at EventEmitter.<anonymous> (/home/ecarroll/n/lib/node_modules/@semantic-release/gitlab/node_modules/got/dist/source/as-promise.js:118:31)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5) {
pluginName: '@semantic-release/gitlab'
}
HTTPError: Response code 400 (Bad Request)
at EventEmitter.<anonymous> (/home/ecarroll/n/lib/node_modules/@semantic-release/gitlab/node_modules/got/dist/source/as-promise.js:118:31)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5) {
pluginName: '@semantic-release/gitlab'
}%
this error, such that I could see,
{
responseType: 'text',body: '{"message":"Validation failed: Links have duplicate values (cpanel-angular-validators.js) for #\\u003cRelease:0x00007f0702a43908\\u003e scope"}'}```**Note this ticket is for displaying the body of an error response to the user**
The text was updated successfully, but these errors were encountered:
I am able to show that
as-promise.js
has a silent failure mode where the body of the request that results in an error is not displayed to the user.This is not the right place to solve this problem, but I could prove the body was not being reflected to the user by modifying this,
This gave me much needed contextual information about
this error, such that I could see,
The text was updated successfully, but these errors were encountered: