search

heroku / heroku-releases-retry

CLI plugin to allow retrying the latest release-phase command
81 stars 7 forks source link

Running command fails with "Cannot read property 'id' of null" #8

Open anthonator opened 5 years ago

anthonator commented 5 years ago

We're getting the following error whenever we try to run releases:retry.

Cannot read property 'id' of null
Error: ENOENT: no such file or directory, open '/Users/tyranthosaur/.cache/heroku/error.log'
    at Object.openSync (fs.js:448:3)
    at Object.writeFileSync (fs.js:1210:35)
    at Object.appendFileSync (fs.js:1256:6)
    at log (/Users/tyranthosaur/.local/share/heroku/node_modules/heroku-cli-util/lib/errors.js:87:6)
    at handleErr (/Users/tyranthosaur/.local/share/heroku/node_modules/heroku-cli-util/lib/errors.js:102:9)
    at processTicksAndRejections (internal/process/next_tick.js:81:5)

I ran across this issue https://github.com/heroku/heroku-releases-retry/issues/6 but it seems unrelated as we have a lot of releases for the app we're trying to use this with.

hugorut commented 5 years ago

having this issue also

dmathieu commented 5 years ago

The missing error.log file seems like a global CLI issue. @heroku/cli.

dmathieu commented 5 years ago

Can you run the command with HEROKU_DEBUG=1 ?

anthonator commented 5 years ago

Is there a way I can share the result privately?

dmathieu commented 5 years ago

You can open a support ticket.

jdx commented 5 years ago

the error thing is a red herring, it just means it wasn't able to write the error out to the old log file. It can be fixed by updating heroku-cli-util, but it won't fix the actual problem—just the error logging.

anthonator commented 5 years ago

How do I update heroku-cli-util when the CLI is installed via homebrew?

jdx commented 5 years ago

you can't but if you just run mkdir -p /Users/tyranthosaur/.cache/heroku it will fix that logging error. Again, not fixing whatever the actual issue is.

m1kola commented 5 years ago

It looks like the issue we had with container apps. It doesn't look like there is an easy way to retry a release with container images on Heroku. You need to build and push a new image. I added some documentation in #11

bbugh commented 4 years ago

Does a review app count as a container app? We're getting this issue on our review apps as well, but we don't use containers.

dmathieu commented 4 years ago

Container apps are apps running on docker. Your review apps won't run on docker unless you're using heroku.yml configuration.