Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's a couple solutions, the easiest of which would be to try running <code>bundle exec cucumber</code> first, and see if that solves your problem.</p> <p>If that doesn't work, delete your rails3tutorial gemset and re-create it again:</p> <pre><code>rvm gemset delete rails3tutorial rvm 1.9.2-p290@rails3tutorial --create </code></pre> <p>Then run <code>bundle</code>, and hopefully it will install your gems for you. Follow this up with <code>bundle exec cucumber</code> (I almost always run my specs and cukes using <code>bundle exec</code> so that it doesn't try accidentally loading stale gems).</p> <p>Hopefully this works!</p> <p>UPDATE: Explaining <code>bundle exec</code> a little more</p> <p><code>bundle exec</code> is a command that bundler comes with that will run any other command in the context of your Gemfile. In this case, you're essentially telling it to run the <code>cucumber</code> command but <em>only</em> with the gems from your Gemfile, and not with all the gems currently available.</p> <p>For instance, if you have previously installed <code>activesupport 3.2.1</code>, and your Gemfile asks for <code>activesupport 3.1.0</code>. When this happens I believe the cucumber command itself pulls in 'activesupport' (maybe via the <code>require 'cucumber/rails'</code> call in env.rb) which grabs any random version of activesupport it can (let's say it grabs 3.2.1) from your available gems. After this, it decides to load up your rails environment to start running your features. When it starts loading your actual app, the code looks at your Gemfile.lock and sees that what you actually want is <code>activesupport 3.1.0</code>, but it can't load an old version on top of a new version, so it crashes with the error James Lin pasted.</p> <p>This is why, if you're using rvm, it's a good idea to keep separate gemsets for your separate projects, and delete/re-create the gemsets if you're updating your gems on that project so you don't keep old versions of gems around. Alternatively, <code>bundle exec</code> tends to solve 99% of the problems as well. If you aren't using rvm, and have multiple projects, then you probably have many different versions of many different gems, and you should always use <code>bundle exec</code> to do things like execute rake tasks, run cucumer features and other unit tests, etc.</p>
    singulars
    1. This table or related slice is empty.
    1. PORuby on Rails - error when running cucumber: You have already activated activesupport 3.2.1, but your Gemfile requires activesupport 3.1.0.
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USnzifnab
    1. USnzifnab
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORuby on Rails - error when running cucumber: You have already activated activesupport 3.2.1, but your Gemfile requires activesupport 3.1.0.
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks running bundle exec cucumber worked!
      singulars
      1. PO
      1. USJames Lin
    2. COCan you explain what is the difference between "cucumber" and "bundle exec cucumber"?
      singulars
      1. PO
      1. UScoelhudo
    3. CO@coelhudo I put the explanation at the end of my answer :)
      singulars
      1. PO
      1. USnzifnab
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload