-
Notifications
You must be signed in to change notification settings - Fork 380
heroku command line fails #1590
Comments
Removing the heroku-repo causes new error. All plugins have been reinstalled, including the heroku toolbelt itself. -bash-4.1$ heroku apps
-bash-4.1$ |
-bash-4.1$ heroku --version |
this likely means there is a json parsing error. Can you run the following?
|
I get the following, looks like a successful outcome. -bash-4.1$ ruby -r json -e "p JSON.parse('{}')" |
Is there a way to turn on some debug logs, which would help to trace where the issues is. So far I've removed and reinstalled all apps and heroku tool-belt itself, without any effect. I've removed the .heroku folder as well, and .netrc file, which re-initiated the login process. Authentication kelp failing, even though I could still successfully sign into the account on other systems and through the UI. |
yeah you can run it with |
it's possible the API may be returning invalid JSON. I'm assuming that's what it is since it is expecting an array but getting a string. The JSON parser catches exceptions and just returns the original string in that case. |
Seems I could not find a solution to this issue, and had to rebuild the machine. Thankfully its' done with Ansible. :) |
heroku ps -a ps-ice4m-latest
! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Error: no time information in "allow_until" (ArgumentError)
Command: heroku ps -a ps-ice4m-latest
Plugins: heroku-repo
Version: heroku-toolbelt/3.37.2 (x86_64-linux-gnu) ruby/2.1.5
Error ID: 944240d697ba4c25887caf409cdc30f3
More information in /opt/jenkins/jenkins_home/.heroku/error.log
The text was updated successfully, but these errors were encountered: