Databases
StackOverflow2013
Postsdbo
POIs this a bug in minitest, sprockets-rails, or ruby-2?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs this a bug in minitest, sprockets-rails, or ruby-2?
    primarykey
    data
    text
    <p>I wanted to patch a bug in sprockets-rails, but when I ran the test suite (using ruby-2.0.0-p0 as well as ruby-head), I got the following error:</p> <pre><code>/Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `block in _prepare_run': undefined method `size' for #&lt;ParallelEach:0x007f823aa55e88&gt; (NoMethodError) from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `each' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `inject' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `_prepare_run' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:648:in `_run_suites' from /Users/btaitelb/.rvm/gems/ruby-head@rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:861:in `_run_anything' from /Users/btaitelb/.rvm/gems/ruby-head@rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1068:in `run_tests' from /Users/btaitelb/.rvm/gems/ruby-head@rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1055:in `block in _run' from /Users/btaitelb/.rvm/gems/ruby-head@rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1054:in `each' from /Users/btaitelb/.rvm/gems/ruby-head@rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1054:in `_run' from /Users/btaitelb/.rvm/gems/ruby-head@rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1042:in `run' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:21:in `run' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:774:in `run' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:834:in `run' from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:838:in `run' from /Users/btaitelb/.rvm/rubies/ruby-head/bin/testrb:7:in `&lt;main&gt;' </code></pre> <p>I'm not clear on the relationship between Test::Unit and MiniTest, especially since I see test/unit.rb referencing MiniTest::Unit</p> <p>I can patch this issue in a couple ways, but I'm not sure which project is to blame (e.g. where I should submit the patch):</p> <ol> <li>In test/unit.rb in ruby, I can replace the call to <code>size</code> with a call to <code>count</code>, but this only seems appropriate if <code>Test::Unit</code> expects a <code>ParallelEach</code> being part of the test suite</li> <li>In minitest, I can alias <code>count</code> to <code>size</code>, which makes sense if minitest is responsible for sending <code>ParallelEach</code> objects to <code>Test::Unit</code></li> </ol> <p>Are either of these appropriate, or is there something else going on here (like a naming conflict)?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBen Taitelbaum
    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
    1. VO
      singulars
      1. POIs this a bug in minitest, sprockets-rails, or ruby-2?
      1. USAlric
      1. VTFavorite
    2. VO
      singulars
      1. POIs this a bug in minitest, sprockets-rails, or ruby-2?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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