Databases
StackOverflow2013
Postsdbo
POruby 1.9.2 strange warning when running cucumber specs
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POruby 1.9.2 strange warning when running cucumber specs
    primarykey
    data
    text
    <p>I just updated to try rails 3, using rvm with ruby 1.9.2-p0.</p> <p>When I run my cucumber specs then I get following strange warnings</p> <pre><code>/home/ubuntu/.rvm/gems/ruby-1.9.2-p0/gems/rack-1.2.1/lib/rack/utils.rb:16: warning: regexp match /.../n against to UTF-8 string /home/ubuntu/.rvm/gems/ruby-1.9.2-p0/gems/rack-1.2.1/lib/rack/utils.rb:16: warning: regexp match /.../n against to UTF-8 string /home/ubuntu/.rvm/gems/ruby-1.9.2-p0/gems/rack-1.2.1/lib/rack/utils.rb:16: warning: regexp match /.../n against to UTF-8 string </code></pre> <p>My bundle contains following gems...</p> <pre><code>Using rake (0.8.7) Using abstract (1.0.0) Using activesupport (3.0.0) Using builder (2.1.2) Using i18n (0.4.1) Using activemodel (3.0.0) Using erubis (2.6.6) Using rack (1.2.1) Using rack-mount (0.6.13) Using rack-test (0.5.4) Using tzinfo (0.3.23) Using actionpack (3.0.0) Using mime-types (1.16) Using polyglot (0.3.1) Using treetop (1.4.8) Using mail (2.2.5) Using actionmailer (3.0.0) Using arel (1.0.1) Using activerecord (3.0.0) Using activeresource (3.0.0) Using bundler (1.0.0) Using culerity (0.2.12) Using nokogiri (1.4.3.1) Using ffi (0.6.3) Using json_pure (1.4.6) Using rubyzip (0.9.4) Using selenium-webdriver (0.0.28) Using capybara (0.3.9) Using configuration (1.1.0) Using diff-lcs (1.1.2) Using trollop (1.16.2) Using gherkin (2.1.5) Using term-ansicolor (1.0.5) Using cucumber (0.8.5) Using cucumber-rails (0.3.2) Using database_cleaner (0.5.2) Using launchy (0.3.7) Using mysql2 (0.2.3) Using rspec-core (2.0.0.beta.20) Using rspec-expectations (2.0.0.beta.20) Using rspec-mocks (2.0.0.beta.20) Using rspec (2.0.0.beta.20) Using yard (0.6.0) Using pickle (0.4.2) Using thor (0.14.0) Using railties (3.0.0) Using rails (3.0.0) Using rspec-rails (2.0.0.beta.20) Using spork (0.8.4) Using webrat (0.7.1) </code></pre> <p>does anyone know how to get rid of these warnings? And where they are coming from?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USIan Vaughan
    1. USserver info
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POruby 1.9.2 strange warning when running cucumber specs
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POruby 1.9.2 strange warning when running cucumber specs
      1. USBo Jeanes
      1. VTFavorite
    3. VO
      singulars
      1. POruby 1.9.2 strange warning when running cucumber specs
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm having exactly the same thing. I'd love to find out the cause!
      singulars
      1. POruby 1.9.2 strange warning when running cucumber specs
      1. USBo Jeanes
    2. COHi there - would you mind checkout out the last answer given to this: http://stackoverflow.com/questions/3622394/ruby-1-9-2-strange-warning-when-running-cucumber-specs/7189698#7189698 I believe it fixes your issue and would be grateful if you could mark it as correct. Ty
      singulars
      1. POruby 1.9.2 strange warning when running cucumber specs
      1. USPeter Nixey
 

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