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

[Bug] HTTPError when committing files #114

Closed
yagueto opened this issue Feb 6, 2022 · 3 comments
Closed

[Bug] HTTPError when committing files #114

yagueto opened this issue Feb 6, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@yagueto
Copy link

yagueto commented Feb 6, 2022

Describe the bug

When it tries to commit the changes, it fails with an UnhandledPromiseRejectionWarning

How To Reproduce

Steps to reproduce the behavior:

  1. Go to logs
  2. Scroll down to 'Compress images', and then 'Committing Files...'
  3. See error:
UnhandledPromiseRejectionWarning: HttpError: request to https://api.github.com/repos/[my username]/[my repo]/git/blobs failed, reason: read ECONNRESET
    at /usr/local/src/image-actions/node_modules/@octokit/request/lib/request.js:94:13
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Expected behaviour

Should add a commit to the PR 🙃

Screenshots

image

Additional context

Also note that the repo is private; however, yesterday was working nicely.
When I click in the URL that it provides, it shows a 404 page

@yagueto yagueto added the bug Something isn't working label Feb 6, 2022
@benschwarz
Copy link
Member

Closing as a dupe of #32

@yagueto
Copy link
Author

yagueto commented Feb 8, 2022

Closing as a dupe of #32

Is it related to this? In this case it doesn’t look like a rate limit, but rather an issue with an inexistent URL. Also, this is strange as I had used it before successfully, and this PR removed multiple images 😅

@benschwarz
Copy link
Member

@yagueto The URL isn't a navigable page, it's only for use in the API. The promise rejection is likely a timeout (or rate limit) due to the number of blobs being committed. I still believe it's a dupe of #32.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants