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

Error when using heroku repo:gc -a appname #95

Open
YashRunwal opened this issue May 2, 2020 · 11 comments
Open

Error when using heroku repo:gc -a appname #95

YashRunwal opened this issue May 2, 2020 · 11 comments

Comments

@YashRunwal
Copy link

When I try to run following command

heroku repo:gc -a indian-notes-classifier

It gives me following error:

The requested URL returned error: 404 Not Found

Why is that and how can i solve this?

@Soumi7
Copy link

Soumi7 commented May 25, 2020

I am having the same error. Did Anyone find a way to resolve the issue?

@AdarshPan
Copy link

I am also having the same error . Any Updates? It's urgent!!

@Soumi7
Copy link

Soumi7 commented Jun 3, 2020

No! None! The mainterners of this repo havent answered.

@edmorley
Copy link
Member

edmorley commented Jun 3, 2020

For urgent issues I would recommend opening a support ticket:
https://help.heroku.com/

@AdarshPan
Copy link

I have already opened a ticket just now ...let's hope for the best
@edmorley Thanks for the link and the suggestion.

@AdarshPan
Copy link

Guys ...... You got any updates??
no update in the ticket yet.....

@parthrangarajan
Copy link

Hey, any updates?!

@edmorley
Copy link
Member

edmorley commented Apr 5, 2021

If you get "404 Not Found" when running heroku repo:gc it means the Git repository for the app does not exist.

This can be the case for:

  • apps have never been deployed via git push (for example apps that only use GitHub sync or another deployment method)
  • apps where the Git repo was deleted - for example by running heroku repo:reset

Regardless of the reason, the fact that the repo doesn't exist means that there's no need to GC it (GC cleans up an existing repo, but if there is no repo, no cleanup is needed).

Out of curiosity, how are people ending up here? Is there a guide/FAQ saying to heroku repo:gc for troubleshooting? If so, there's likely a better way to fix the underlying issue. For example use heroku repo:reset to just delete the repo and start fresh, or if you want to clear the build cache (eg to solve a build problem or reduce slug size bloat in certain cases), then use this other plugin/command instead:
https://github.com/heroku/heroku-builds#purge-build-cache

@patrik-csak
Copy link

I ended up here from How To Reduce a Large Heroku Slug Size (thoughtbot.com) after purging the build cache failed to reduce my slug to under 500M

@nhungL
Copy link

nhungL commented Aug 25, 2023

@patrik-csak were you able to solve it eventually? I'm having both the slug size issue and 404 not found

@patrik-csak
Copy link

@nhungL iirc, i re-architected my project to make it smaller

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

7 participants