Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

cannot start console #1

Open
michaelkirk opened this issue Aug 28, 2013 · 1 comment
Open

cannot start console #1

michaelkirk opened this issue Aug 28, 2013 · 1 comment

Comments

@michaelkirk
Copy link

Are you seeing this @rwdaigle ?

heroku run rails c
Running `rails c` attached to terminal... up, run.1879
/app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:296:in `to_specs': Could not find 'sprockets' (~> 2.2.1) among 131 total gem(s) (Gem::LoadError)
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1196:in `block in activate_dependencies'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1185:in `each'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1185:in `activate_dependencies'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1167:in `activate'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1199:in `block in activate_dependencies'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1185:in `each'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1185:in `activate_dependencies'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:1167:in `activate'
    from /app/vendor/ruby-2.0.0/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:48:in `gem'
    from /app/vendor/bundle/ruby/2.0.0/bin/rails:22:in `<main>'

Note: I am based on master as of today - I suspect (but have not confirmed) that it's related to the newish plugin booting process.
@rwdaigle
Copy link
Owner

@michaelkirk I do see this behavior when executing rails c directly. Try running it with bundle exec instead?

$ heroku run bundle exec rails c
...
Loading production environment (Rails 3.2.12)
irb(main):001:0>

rwdaigle pushed a commit that referenced this issue Nov 4, 2013
@SamSaffron
automatically make developers admins on account creation, this solves…
8ff35d4 
… the user #1 problem

you can simply set the DEVELOPER_EMAILS to a comma delimited list and the users will be auto admined
rwdaigle added a commit that referenced this issue Nov 4, 2013
@rwdaigle
Merge remote-tracking branch 'upstream/master'
1868cb6 
* upstream/master: (25 commits)
  FIX: Don't autolink within a markdown link.
  missing semi colon
  FIX: Some more non-english category errors
  FIX: Show status icons on user topic pages
  FIX: issue 1538. After upgrading and before a new version check request has been made, dashboard might still say that an update is available.
  fixing user title line-height, adding @mention style back in, consistent category width/alignment
  FIX: emoticon 💩 wasn't working :)
  some general simplification to modal, menus, etc
  revert changes to magnific-popup.scss
  FIX issues with quote button
  shorter message for untranslated strings
  Rails 4 changes behavior of precompile not to include originals This patch will restore rails 3 beavior and fix emoji etc under rails 4
  Update client.nl.yml
  Update server.nl.yml
  Dont call `SiteSetting.uncategorized_category_id` twice
  Fix ActiveRecord::Associations::CollectionProxy serialization in Rails 4.
  Update client.zh_CN.yml
  automatically make developers admins on account creation, this solves the user #1 problem you can simply set the DEVELOPER_EMAILS to a comma delimited list and the users will be auto admined
  fix run-qunit
  add qunit to autospec
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rwdaigle @michaelkirk