We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We were trying to deploy with heroku san, and it was hanging with no feedback. When we Ctrl-C'ed, we got this stack trace:
^Crake aborted! /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:137:in ``' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:137:in `auth_token' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:20:in `heroku' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:80:in `maintenance' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:193:in `block (3 levels) in <top (required)>' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:63:in `block in each_app' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:62:in `each' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:62:in `each_app' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:321:in `each_heroku_app' /Users/pivotal/.rvm/gems/ruby-1.9.3-p194@portal/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:192:in `block (2 levels) in <top (required)>'
We then re-authed with heroku login, and everything started working.
heroku login
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We were trying to deploy with heroku san, and it was hanging with no feedback. When we Ctrl-C'ed, we got this stack trace:
We then re-authed with
heroku login
, and everything started working.The text was updated successfully, but these errors were encountered: