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
hi,
the action sent the post request successfully but there's no response displayed. also seen the error message below:
(node:2444) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'code' of undefined
at /home/runner/work/_actions/fjogeleit/http-request-action/master/dist/index.js:2656:58
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:2444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:2444) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered:
I updated the error handling, so you should now get detailed information why the API call is rejected. You can use the new version with the "latest" or "v1.3.1" Tag
hi,
the action sent the post request successfully but there's no response displayed. also seen the error message below:
(node:2444) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'code' of undefined
at /home/runner/work/_actions/fjogeleit/http-request-action/master/dist/index.js:2656:58
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:2444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:2444) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: