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: Bad credentials #38

Open
u0324020 opened this issue Aug 25, 2021 · 1 comment
Open

UnhandledPromiseRejectionWarning: HttpError: Bad credentials #38

u0324020 opened this issue Aug 25, 2021 · 1 comment

Comments

@u0324020
Copy link

Workflow:
- uses: toko-bifrost/ms-teams-deploy-card@3.1.2 if: always() with: github-token: ${{ secrets.GIT_TOKEN }} webhook-uri: ${{ secrets.MS_TEAMS_WEBHOOK_URI }} environment: dev # won't be included in the card if none timezone: Asia/Taipei view-status-action-text: View in Actions review-diffs-action-text: Review Commit Diffs

Error:
(node:145712) UnhandledPromiseRejectionWarning: HttpError: Bad credentials 19 at /home/runner/actions-runner/_work/_actions/toko-bifrost/ms-teams-deploy-card/3.1.2/dist/main/index.js:1:462593 20 at processTicksAndRejections (internal/process/task_queues.js:93:5) 21 at async getOctokitCommit (/home/runner/actions-runner/_work/_actions/toko-bifrost/ms-teams-deploy-card/3.1.2/dist/main/index.js:1:36969) 22 at async Object.formatAndNotify (/home/runner/actions-runner/_work/_actions/toko-bifrost/ms-teams-deploy-card/3.1.2/dist/main/index.js:1:37465) 23 (node:145712) 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: 1) 24 (node:145712) [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.

@rokeno
Copy link

rokeno commented Nov 14, 2022

i have the same thing. No idea if it's the msteams incoming webhook or the github token (which has been regenerated with full credentials)

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

2 participants