Open davidsoul opened 11 years ago
This is a confirmed bug that is most reproducible with kappa and crane dbs. Looking at the backtrace, the fork command is not getting the expected message from the addon:add command to parse. For production dbs, the wait for this message can be 5-10 seconds, and if fork is not waiting, it will fail. dev/basic and ronin up dbs are able to return faster, but may also fail.
Attempting to fork a Heroku org app 'heroku-data-warehouse-coresfdc' fails for me on the postgres addnon. Error message.
Davids-MacBook-Air:Development soul$ heroku fork -a heroku-data-warehouse-coresfdc heroku-data-warehouse-scripts Creating fork heroku-data-warehouse-scripts... done Copying slug... done Adding scheduler:standard... done Adding heroku-postgresql:dev... skipped (Could not communicate with vendor, please try again later)
! Heroku client internal error. ! Search for help at: https://help.heroku.com ! Or report a bug at: https://github.com/heroku/heroku/issues/new