Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnhandledPromiseRejectionWarning: HttpError #43

Open
liquidkey opened this issue Feb 17, 2022 · 2 comments
Open

UnhandledPromiseRejectionWarning: HttpError #43

liquidkey opened this issue Feb 17, 2022 · 2 comments

Comments

@liquidkey
Copy link

Hi

I am getting the below error

(node:109) UnhandledPromiseRejectionWarning: HttpError: request to https://api.github.com/repos/GlobeOp/gopricingml/commits/4deb107c56f1419f0f849394dde9aa5ce7c87da1 failed, reason: connect ETIMEDOUT 140.82.112.6:443
at /__w/_actions/toko-bifrost/ms-teams-deploy-card/master/dist/main/index.js:1:463063
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async getOctokitCommit (/__w/_actions/toko-bifrost/ms-teams-deploy-card/master/dist/main/index.js:1:36969)
at async Object.formatAndNotify (/__w/_actions/toko-bifrost/ms-teams-deploy-card/master/dist/main/index.js:1:37465)
(node:109) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:109) [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.

@dchourasia
Copy link

@liquidkey we are facing the same error where its is posting the start-card but not the exit-card and throwing this exception in stead... did you find any resolution to this issue

@stevie-
Copy link

stevie- commented Nov 29, 2022

Hi

I am getting the below error

(node:109) UnhandledPromiseRejectionWarning: HttpError: request to https://api.github.com/repos/GlobeOp/gopricingml/commits/4deb107c56f1419f0f849394dde9aa5ce7c87da1 failed, reason: connect ETIMEDOUT 140.82.112.6:443 at /__w/_actions/toko-bifrost/ms-teams-deploy-card/master/dist/main/index.js:1:463063 at processTicksAndRejections (internal/process/task_queues.js:97:5) at async getOctokitCommit (/__w/_actions/toko-bifrost/ms-teams-deploy-card/master/dist/main/index.js:1:36969) at async Object.formatAndNotify (/__w/_actions/toko-bifrost/ms-teams-deploy-card/master/dist/main/index.js:1:37465) (node:109) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:109) [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.

Seems like your runner can't connect to github api:

reason: connect ETIMEDOUT 140.82.112.6:443

Another issue one may see here is a permissions error if you set permissions in your workflow.
This action requires

permissions:
 actions: read

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants