`heroku local` fails when process type contains dashes

[ed-wong]

Bug

heroku local fails to parse the Procfile when the process type contains a dash. I noticed that after changing the dashes to underscores instead, it works. This was previously working in v10.17.0 and failed when I updated to v11.1.1.

When deploying on Heroku, I didn't encounter any issues. My workaround for now is to use foreman directly and run foreman start.

Example Procfile

web: bundle exec puma -C config/puma.rb
worker-primary: bundle exec sidekiq --config config/sidekiq.yml

Current Behaviour

I encounter a parse error when running heroku local.

Error Message: Error: line 2 parse error: worker-primary: bundle exec sidekiq --config config/sidekiq.yml

Expected Behaviour

The Procfile is parsed and runs successfully when the process type contains dashes.

[k80bowman]

@ed-wong thank you for bringing this to us. Would you mind checking if v11.2.0 of the CLI fixes this issue for you? I believe it should, but I'm not sure we tested this particular scenario so I want to be sure before I close this issue. Thank you!

[ed-wong]

@k80bowman Just checked and the issue seems to be resolved now. Thanks for the quick resolution!

Correction: the issue still seems to be present in v11.2.0. We were experimenting with changes with the Procfile, which got it working, but it is still only a workaround and the issue with Heroku CLI remains.

[k80bowman]

Thank you so much for letting us know! We will take a look.

[maksp-lipscore]

Hi, I just noticed this issue as well on the latest version. I’m running multiple workers via my Procfile. Do you have plans to fix it?

Thanks!