Bug 1631099 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
some examples of this error:

```
 message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Object.<anonymous> (/app/services/github/src/api.js:293:22)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.statusHandler (/app/services/github/src/handlers.js:528:7)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.deprecatedStatusHandler (/app/services/github/src/handlers.js:419:5)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.taskDefinedHandler (/app/services/github/src/handlers.js:878:20)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.statusHandler (/app/services/github/src/handlers.js:508:7)" 
```

All of them come from the retry function. The earliest version I can see this in is "v28.0.0". It was released on March 12. Deployed to Firefox CI on April 13. Dustin brought this to my attention on Apr 8, mentioning he had seen it some weeks before (in community cluster). Aki reported this on Apr 17 (also after seeing it several times.)

The v28.0.0 release introduced change in logging. My current theory is that we over-report this error during the retries for some reason.
Revision 1 by
on 
some examples of this error:

```
 message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Object.<anonymous> (/app/services/github/src/api.js:293:22)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.statusHandler (/app/services/github/src/handlers.js:528:7)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.deprecatedStatusHandler (/app/services/github/src/handlers.js:419:5)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.taskDefinedHandler (/app/services/github/src/handlers.js:878:20)"   

    message: "HttpError: Bad credentials
    at /app/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /app/services/github/src/github-auth.js:12:16
    at async Handlers.statusHandler (/app/services/github/src/handlers.js:508:7)" 
```

All of them come from the retry function. The earliest version I can see this in is "v28.0.0". It was released on March 12. Deployed to Firefox CI on April 13. Dustin brought this to my attention on Apr 8, mentioning he had seen it some weeks before (in community cluster). Aki reported this on Apr 17 (also after seeing it several times.)

The v28.0.0 release introduced change in logging. My current theory is that we now over-report this error during the retries.

Back to Bug 1631099 Comment 3