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

heroku pg:diagnose Not working #3160

Closed
ahteshamtariq opened this issue Jan 5, 2025 · 3 comments
Closed

heroku pg:diagnose Not working #3160

ahteshamtariq opened this issue Jan 5, 2025 · 3 comments

Comments

@ahteshamtariq
Copy link

Bug Report

When ever I run heroku pg:diagnose it's giving this error:

TypeError: Cannot read properties of undefined (reading 'exitCode')

When I run HEROKU_DEBUG=1 heroku pg:diagnose it shows:

TypeError: Cannot read properties of undefined (reading 'exitCode')
    at Diagnose.catch (/opt/homebrew/Cellar/heroku/10.0.0/libexec/lib/node_modules/heroku/node_modules/@oclif/core/lib/command.js:226:52)
    at Diagnose._run (/opt/homebrew/Cellar/heroku/10.0.0/libexec/lib/node_modules/heroku/node_modules/@oclif/core/lib/command.js:121:29)
    at async Config.runCommand (/opt/homebrew/Cellar/heroku/10.0.0/libexec/lib/node_modules/heroku/node_modules/@oclif/core/lib/config/config.js:314:25)
    at async Object.run (/opt/homebrew/Cellar/heroku/10.0.0/libexec/lib/node_modules/heroku/node_modules/@oclif/core/lib/main.js:89:16)

heroku-cli version heroku/10.0.0 darwin-arm64 node-v23.5.0

@sbosio
Copy link
Contributor

sbosio commented Jan 6, 2025

Hello @ahteshamtariq,

We have other reports about the same issue and have identified the root cause. A fix is ready to be released this week.

If you're urged to use that command, please downgrade your Heroku CLI with heroku update --version=9.5.1. That will allow you to run the command. Once the release is out with the fixes you can upgrade again to v10 with heroku update stable and verify the command is now working correctly with v10.

We're sorry about the inconveniences this might have caused.

@k80bowman
Copy link
Contributor

We just released v10.0.1 which should fix this issue for you.

@eablack eablack closed this as completed Jan 13, 2025
@ahteshamtariq
Copy link
Author

Yes, Now working thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants