Cli: "dashboard is not a heroku command" when running the command without arguments

[elopio]

I'm testing the heroku cli from master in Ubuntu Xenial. When I run the heroku command with no arguments, I'm getting:

$ heroku
 ▸    dashboard is not a heroku command.
 ▸    Perhaps you meant whoami?
 ▸    Run heroku _ to run heroku whoami.
 ▸    Run heroku help for a list of available commands.

The reference to dashboard is wrong. Maybe the help command should be the default.

I can reproduce it also with:

$ ./bin/run 
Makefile:90: *** mixed implicit and normal rules: deprecated syntax
 ▸    dashboard is not a heroku command.
 ▸    Perhaps you meant whoami?
 ▸    Run heroku _ to run heroku whoami.
 ▸    Run heroku help for a list of available commands.

[dacianmujdar]

did you find a solution for this?

[MattDHill]

No matter what I type into the command line, I'm getting the same response. The happened suddenly and without apparent cause. See below.

heroku help
 ▸    commands is not a heroku command.
 ▸    Perhaps you meant domains
 ▸    Run heroku help for a list of available commands.
 !    error getting commands pid 24643 exit 127

[blakerego]

I'm seeing a similar error when running the console command.

➜ git:(master) heroku console
 ▸    commands is not a heroku command.
 ▸    Perhaps you meant domains
 ▸    Run heroku help for a list of available commands.
 !    error getting commands pid 93422 exit 127

This was working for me yesterday

[brightball]

Exact same thing just started here.

[metaprogrammed]

Same, was working up until an hour ago.

[jackphelps]

We are seeing this too -- significantly affecting some of our engineers' ability to work with our heroku services. Haven't been able to figure anything out yet :/

[brightball]

I've opened a support ticket with Heroku and gotten a response that they are looking into it. No word yet though.

[alnoorp]

I started seeing this same issue right after the Heroku CLI update. Updating heroku with brew install heroku seemed to fix the issue.

[brightball]

Not having any luck on Ubuntu. I tried uninstalling and reinstalling with the same results.

[jackphelps]

Realized that engineers on our team with trouble here (we are all mac users) had the non-homebrew version of the heroku CLI installed. Removing that and installing with homebrew (brew install heroku) fixed the issue for them.

I'm guessing heroku inadvertently made a breaking change to the old heroku toolbelt version of the client, but who knows. Good luck y'all.

[jackphelps]

looks like alnoorp edited his comment and beat me to it :)

[jdxcode]

this is now resolved. If you're still having issues, reinstall from https://cli.heroku.com