1302 0 true 2009-01-18T02:12:54+01:00 12071 165 error-when-not-caching-classes 27231 16211 resolved bug database innodb myisam rails rollback table transaction type world 2009-08-04T15:35:15+02:00 1379 Lee Hambley Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 With config.cache_classes = false in config/environments/test.rb, running 'rake features' with a webrat 'visit' step produces /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17143580' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 7 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:39:in `visit_features' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:159:in `execute!' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:14:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/cucumber:6 rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...] Setting config.cache_classes = true does not produce this error. (Turning off class caching is necessary to use spec_server.) With config.cache_classes = false in config/environments/test.rb, running 'rake features' with a webrat 'visit' step produces /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17143580' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 7 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:39:in `visit_features' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:159:in `execute!' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:14:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/cucumber:6 rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...] Setting config.cache_classes = true does not produce this error. (Turning off class caching is necessary to use spec_server.) <div><p>With</p> <p>config.cache_classes = false</p> <p>in config/environments/test.rb, running 'rake features' with a webrat 'visit' step produces</p> <p> /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in <code>decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/rails/world.rb:60:in</code>__cucumber_17143580'</p> <pre> <code>from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 7 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:39:in `visit_features' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:159:in `execute!' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:14:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/cucumber:6 </code> </pre> <p>rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...]</p> <p>Setting</p> <p>config.cache_classes = true</p> <p>does not produce this error. (Turning off class caching is necessary to use spec_server.)</p></div> 1302 0 With config.cache_classes = false in config/environments/test.rb, running 'rake features' with a webrat 'visit' step produces /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17143580' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 7 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:39:in `visit_features' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:159:in `execute!' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:14:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/cucumber:6 rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...] Setting config.cache_classes = true does not produce this error. (Turning off class caching is necessary to use spec_server.) <div><p>With</p> <p>config.cache_classes = false</p> <p>in config/environments/test.rb, running 'rake features' with a webrat 'visit' step produces</p> <p> /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in <code>decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/rails/world.rb:60:in</code>__cucumber_17143580'</p> <pre> <code>from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 7 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/executor.rb:39:in `visit_features' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:159:in `execute!' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/../lib/cucumber/cli.rb:14:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.15/bin/cucumber:6 </code> </pre> <p>rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...]</p> <p>Setting</p> <p>config.cache_classes = true</p> <p>does not produce this error. (Turning off class caching is necessary to use spec_server.)</p></div> false 2009-01-18T02:12:54+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new 2009-01-18T02:12:59+01:00 12071 Mark Wilden Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Very interesting. Definitely looks like the same issue I was seeing in my rspec-users post: http://rubyforge.org/pipermail/rspec-users/2009-January/011735.html As I noted there, the error went away for me if I commented this line out from my features/support/env.rb file: @@@ Cucumber::Rails.use_transactional_fixtures @@@ On seeing your ticket, I've uncommented it and changed this line in my config/environments/test.rb from: @@@ config.cache_classes = false @@@ To: @@@ config.cache_classes = true @@@ And the error goes away. Interestingly enough, turning on class caching also fixes a problem with FixtureReplacement. With class caching turned off I couldn't use FixtureReplacement in my step definitions at all; a line like: @@@ create_article :title => title @@@ Would produce this error when running the features: @@@ undefined local variable or method `validate' for #<Article:0x34031cc> (NameError) vendor/plugins/fixture_replacement/lib/fixture_replacement/fixture_replacement_generator.rb:68:in `create_article' @@@ Which was a completely bizarre error message to me because evidently an Article instance was being created, and it very definitely understands the "validate" method. So there's something very fishy going on that relates to class caching. <div><p>Very interesting. Definitely looks like the same issue I was seeing in my rspec-users post:</p> <p><a href="http://rubyforge.org/pipermail/rspec-users/2009-January/011735.html"> http://rubyforge.org/pipermail/r...</a></p> <p>As I noted there, the error went away for me if I commented this line out from my features/support/env.rb file:</p> <pre><code> Cucumber::Rails.use_transactional_fixtures </code></pre> <p>On seeing your ticket, I've uncommented it and changed this line in my config/environments/test.rb from:</p> <pre><code> config.cache_classes = false </code></pre> <p>To:</p> <pre><code> config.cache_classes = true </code></pre> <p>And the error goes away.</p> <p>Interestingly enough, turning on class caching also fixes a problem with FixtureReplacement. With class caching turned off I couldn't use FixtureReplacement in my step definitions at all; a line like:</p> <pre><code> create_article :title =&gt; title </code></pre> <p>Would produce this error when running the features:</p> <pre><code> undefined local variable or method `validate' for #&lt;Article:0x34031cc&gt; (NameError) vendor/plugins/fixture_replacement/lib/fixture_replacement/fixture_replacement_generator.rb:68:in `create_article' </code></pre> <p>Which was a completely bizarre error message to me because evidently an Article instance was being created, and it very definitely understands the "validate" method.</p> <p>So there's something very fishy going on that relates to class caching.</p></div> false 2009-01-18T21:25:21+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new 2009-01-18T21:25:24+01:00 12845 Wincent Colaiuta Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I note you are using cucumber 0.15.x. The latest stable gem release is version 0.16.x. Would you mind upgrading and seeing if you still have the same problem. Thanks <div><p>I note you are using cucumber 0.15.x.</p> <p>The latest stable gem release is version 0.16.x.</p> <p>Would you mind upgrading and seeing if you still have the same problem.</p> <p>Thanks</p></div> false 2009-02-17T21:50:17+01:00 12071 --- :tag: 165 error-when-not-caching-classes 0 16211 new bug 2009-02-17T21:50:22+01:00 15301 Joseph Wilk Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I'm using the latest version, 0.1.16, and the problem exists. <div><p>I'm using the latest version, 0.1.16, and the problem exists.</p></div> false 2009-02-17T22:12:25+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-02-17T22:12:31+01:00 12845 Wincent Colaiuta Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 The same error occurs with Cucumber 0.1.16, with a somewhat different backtrace: /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib /active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17000320' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 9 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/cli.rb:13:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/cucumber:6 from /usr/bin/cucumber:19:in `load' from /usr/bin/cucumber:19 <div><p>The same error occurs with Cucumber 0.1.16, with a somewhat different backtrace:</p> <p>/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib /active_record/connection_adapters/abstract_adapter.rb:159:in <code>decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/rails/world.rb:60:in</code>__cucumber_17000320'</p> <pre> <code>from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 9 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/cli.rb:13:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/cucumber:6 from /usr/bin/cucumber:19:in `load' from /usr/bin/cucumber:19 </code> </pre></div> false 2009-02-17T22:13:06+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-02-17T22:13:11+01:00 12071 Mark Wilden Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 The same error occurs with Cucumber 0.1.16, with a somewhat different backtrace: /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17000320' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 9 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/cli.rb:13:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/cucumber:6 from /usr/bin/cucumber:19:in `load' from /usr/bin/cucumber:19 (I'm trying to figure out how to quote stuff in this markup, whatever it is.) <div><p>The same error occurs with Cucumber 0.1.16, with a somewhat different backtrace:</p> <pre> <code>/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) </code> </pre> <p>You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/rails/world.rb:60:in <code>__cucumber_17000320'</code></p> <pre> <code>from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 9 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/cli.rb:13:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/cucumber:6 from /usr/bin/cucumber:19:in `load' from /usr/bin/cucumber:19 </code> </pre> <p>(I'm trying to figure out how to quote stuff in this markup, whatever it is.)</p></div> false 2009-02-17T22:14:55+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-02-17T22:14:57+01:00 12071 Mark Wilden Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Closer. :) /Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17000320' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 9 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/cli.rb:13:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/cucumber:6 from /usr/bin/cucumber:19:in `load' from /usr/bin/cucumber:19 <div><p>Closer. :)</p> <pre> <code>/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:159:in `decrement_open_transactions': You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/rails/world.rb:60:in `__cucumber_17000320' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `__send__' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/core_ext/proc.rb:48:in `call_in' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `each' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:88:in `execute_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:75:in `visit_scenario' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/executor.rb:65:in `visit_regular_scenario' ... 9 levels... from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/../lib/cucumber/cli.rb:13:in `execute' from /Library/Ruby/Gems/1.8/gems/cucumber-0.1.16/bin/cucumber:6 from /usr/bin/cucumber:19:in `load' from /usr/bin/cucumber:19 </code> </pre></div> false 2009-02-17T22:16:01+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-02-17T22:16:03+01:00 12071 Mark Wilden Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I've been testing this on our cucumber_rails test project. I've confirmed that this bug still exists in the latest cucumber (0.1.99.21) against rails 2.2.2. The error we get on 'rake features' is: @@@ /Users/joseph/Workspace/ruby/josephwilk/cucumber_rails/vendor/plugins/cucumber/bin/../lib/cucumber/core_ext/instance_exec.rb:29: cannot rollback - no transaction is active (SQLite3::SQLException) @@@ Cuke uses http://eigenclass.org/hiki/bounded+space+instance_exec There is a delightful comment about problems when using this with ActiveRecord - "Love this, but when using with ActiveRecord I get some very weird side effects". Looking to see if this is at all relevant. <div><p>I've been testing this on our cucumber_rails test project.</p> <p>I've confirmed that this bug still exists in the latest cucumber (0.1.99.21) against rails 2.2.2.</p> <p>The error we get on 'rake features' is:</p> <pre><code> /Users/joseph/Workspace/ruby/josephwilk/cucumber_rails/vendor/plugins/cucumber/bin/../lib/cucumber/core_ext/instance_exec.rb:29: cannot rollback - no transaction is active (SQLite3::SQLException) </code></pre> <p>Cuke uses <a href="http://eigenclass.org/hiki/bounded+space+instance_exec">http://eigenclass.org/hiki/bound...</a> There is a delightful comment about problems when using this with ActiveRecord - "Love this, but when using with ActiveRecord I get some very weird side effects". Looking to see if this is at all relevant.</p></div> false 2009-02-19T16:17:07+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-02-19T16:17:09+01:00 15301 Joseph Wilk Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I also get this error, with the same sort of backtrace. I'm running the latest version. <div><p>I also get this error, with the same sort of backtrace. I'm running the latest version.</p></div> false 2009-03-20T08:04:28+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-03-20T08:04:31+01:00 50219 bolivares (at azavia) Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Can anyone confirm that this is a problem on 0.2.0 too? If not, can you make a patch of the cucumber_rails project on Github that illustrates the bug? <div><p>Can anyone confirm that this is a problem on 0.2.0 too?</p> <p>If not, can you make a patch of the cucumber_rails project on Github that illustrates the bug?</p></div> false 2009-03-20T14:34:35+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-03-20T14:34:41+01:00 1302 Aslak Hellesøy Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 It is still a problem in 0.2.0. $ rake features (in /home/Brandon/projects/project-name) /usr/bin/ruby -I "/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/lib:lib" "/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/cucumber" --format pretty --require features/step_definitions/contact_steps.rb --require features/step_definitions/webrat_steps.rb --require features/support/env.rb --require features/support/paths.rb features/user-contacts-the-company.feature Feature ... /usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/../lib/cucumber/core_ext/instance_exec.rb:29: You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- rake aborted! Command failed with status (1): [/usr/bin/ruby -I "/usr/lib/ruby/gems/1.8/g...] (See full trace by running task with --trace) <div><p>It is still a problem in 0.2.0.</p> <p>$ rake features (in /home/Brandon/projects/project-name) /usr/bin/ruby -I "/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/lib:lib" "/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/cucumber" --format pretty --require features/step_definitions/contact_steps.rb --require features/step_definitions/webrat_steps.rb --require features/support/env.rb --require features/support/paths.rb features/user-contacts-the-company.feature Feature ... /usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/../lib/cucumber/core_ext/instance_exec.rb:29: You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- rake aborted! Command failed with status (1): [/usr/bin/ruby -I "/usr/lib/ruby/gems/1.8/g...]</p> <p>(See full trace by running task with --trace)</p></div> false 2009-03-20T16:09:39+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-03-20T16:09:39+01:00 50219 bolivares (at azavia) Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Oops, formatted incorrectly. Let me try this again: @@@ $ rake features (in /home/Brandon/projects/project-name) /usr/bin/ruby -I "/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/lib:lib" "/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/cucumber" --format pretty --require features/step_definitions/contact_steps.rb --require features/step_definitions/webrat_steps.rb --require features/support/env.rb --require features/support/paths.rb features/user-contacts-the-company.feature Feature ... /usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/../lib/cucumber/core_ext/instance_exec.rb:29: You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- rake aborted! Command failed with status (1): [/usr/bin/ruby -I "/usr/lib/ruby/gems/1.8/g...] (See full trace by running task with --trace) @@@ <div><p>Oops, formatted incorrectly. Let me try this again:</p> <pre><code> $ rake features (in /home/Brandon/projects/project-name) /usr/bin/ruby -I &quot;/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/lib:lib&quot; &quot;/usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/cucumber&quot; --format pretty --require features/step_definitions/contact_steps.rb --require features/step_definitions/webrat_steps.rb --require features/support/env.rb --require features/support/paths.rb features/user-contacts-the-company.feature Feature ... /usr/lib/ruby/gems/1.8/gems/aslakhellesoy-cucumber-0.2.0/bin/../lib/cucumber/core_ext/instance_exec.rb:29: You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.- rake aborted! Command failed with status (1): [/usr/bin/ruby -I &quot;/usr/lib/ruby/gems/1.8/g...] (See full trace by running task with --trace) </code></pre></div> false 2009-03-20T16:15:31+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-03-20T16:15:32+01:00 50219 bolivares (at azavia) Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I don't think there is much to do about this in Cucumber. This is all Rails weirdness. I have done a small change to World so that error messages are hopefully a little better. <div><p>I don't think there is much to do about this in Cucumber. This is all Rails weirdness. I have done a small change to World so that error messages are hopefully a little better.</p></div> false 2009-03-20T21:23:33+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 new bug 2009-03-20T21:23:34+01:00 1302 Aslak Hellesøy Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 (from [0c999d29207c6eb4ee107e5230c89127eac575c6]) Better error message when config.cache_classes = true. [#165 state:open] http://github.com/aslakhellesoy/cucumber/commit/0c999d29207c6eb4ee107e5230c89127eac575c6 <div><p>(from [0c999d29207c6eb4ee107e5230c89127eac575c6]) Better error message when config.cache_classes = true. [<a href="/projects/16211/tickets/165" title="Ticket #165">#165</a> state:open] <a href="http://github.com/aslakhellesoy/cucumber/commit/0c999d29207c6eb4ee107e5230c89127eac575c6"> http://github.com/aslakhellesoy/...</a></p></div> false 2009-03-20T21:41:57+01:00 12071 --- :state: new 165 error-when-not-caching-classes 0 16211 open bug 2009-03-20T21:41:58+01:00 1302 Aslak Hellesøy Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I also tested against 0.2.0. With class caching on, all the features run fine. With class caching off, we fail like this: @@@Feature: annotated changes to issue metadata As a user I want changes to issue metadata to be annotated as comments So that I can see how the issue has changed over time Scenario: I change an issue summary # features/issues.feature:6 Given an issue with summary "foo" # features/step_definitions/issues.rb:1 When I am logged in as an admin user # features/step_definitions/common.rb:1 And I edit the issue with summary "foo" # features/step_definitions/issues.rb:13 edit_issue_url failed to generate from {:controller=>"issues", :protocol=>"https", :action=>"edit", :id=>nil}, expected: {:controller=>"issues", :protocol=>"https", :action=>"edit"}, diff: {:id=>nil} (ActionController::RoutingError) (eval):16:in `edit_issue_path' ./features/step_definitions/issues.rb:14:in `/^I edit the issue with summary "(.*)"$/' features/issues.feature:9:in `And I edit the issue with summary "foo"' And I change the summary to "bar" # features/step_definitions/issues.rb:17 And I submit my changes to the issue # features/issues.feature:11 Then I should see "Summary changed" # features/step_definitions/webrat_steps.rb:89 /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/core_ext/instance_exec.rb:29: You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.-rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...] (See full trace by running task with --trace) @@@ So these are not exactly the same problems I saw in past versions of Cucumber, but there are some problems nonetheless. Namely, spurious routing errors getting raised, and the "nil object when you didn't expect it" thing. Unfortunately it's a little bit difficult to know where this all started. When I first started using Cucumber it worked, then at some point it stopped working and I don't know whether the breakage was due to a change in Rails or a change in Cucumber... In any case, in the meantime, running with class caching on fixes everything. <div><p>I also tested against 0.2.0. With class caching on, all the features run fine. With class caching off, we fail like this:</p> <p>@@@Feature: annotated changes to issue metadata As a user I want changes to issue metadata to be annotated as comments So that I can see how the issue has changed over time</p> <p>Scenario: I change an issue summary # features/issues.feature:6</p> <pre> <code>Given an issue with summary "foo" # features/step_definitions/issues.rb:1 When I am logged in as an admin user # features/step_definitions/common.rb:1 And I edit the issue with summary "foo" # features/step_definitions/issues.rb:13 edit_issue_url failed to generate from {:controller=&gt;"issues", :protocol=&gt;"https", :action=&gt;"edit", :id=&gt;nil}, expected: {:controller=&gt;"issues", :protocol=&gt;"https", :action=&gt;"edit"}, diff: {:id=&gt;nil} (ActionController::RoutingError) (eval):16:in `edit_issue_path' ./features/step_definitions/issues.rb:14:in `/^I edit the issue with summary "(.*)"$/' features/issues.feature:9:in `And I edit the issue with summary "foo"' And I change the summary to "bar" # features/step_definitions/issues.rb:17 And I submit my changes to the issue # features/issues.feature:11 Then I should see "Summary changed" # features/step_definitions/webrat_steps.rb:89 </code> </pre> <p> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/core_ext/instance_exec.rb:29: You have a nil object when you didn't expect it! (NoMethodError) You might have expected an instance of Array. The error occurred while evaluating nil.-rake aborted! Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...]</p> <p>(See full trace by running task with --trace)</p> <pre><code> So these are not exactly the same problems I saw in past versions of Cucumber, but there are some problems nonetheless. Namely, spurious routing errors getting raised, and the &quot;nil object when you didn't expect it&quot; thing. Unfortunately it's a little bit difficult to know where this all started. When I first started using Cucumber it worked, then at some point it stopped working and I don't know whether the breakage was due to a change in Rails or a change in Cucumber... In any case, in the meantime, running with class caching on fixes everything. </code></pre></div> false 2009-03-21T15:53:51+01:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug 2009-03-21T15:53:55+01:00 12845 Wincent Colaiuta Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 This issue makes Cucumber incompatible with spec_server. spec_server requires config.cache_classes == false. Cucumber features can fail when config.cache_classes == true. Anyone who has gotten used to running a spec in under a second with spec_server will recognize the importance of this problem. So far, my best idea is to set config.cache_classes based on an environment variable that's set based on whether specs or features are being run. <div><p>This issue makes Cucumber incompatible with spec_server. spec_server requires config.cache_classes == false. Cucumber features can fail when config.cache_classes == true.</p> <p>Anyone who has gotten used to running a spec in under a second with spec_server will recognize the importance of this problem. So far, my best idea is to set config.cache_classes based on an environment variable that's set based on whether specs or features are being run.</p></div> false 2009-04-02T19:17:23+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug 2009-04-02T19:17:26+02:00 12071 Mark Wilden Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 What if the Cucumber generator created a new cucumber environment and ran with that as default? <div><p>What if the Cucumber generator created a new cucumber environment and ran with that as default?</p></div> false 2009-04-02T19:36:14+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug 2009-04-02T19:36:18+02:00 1302 Aslak Hellesøy Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Since the value of `config.cache_classes` only matters to spec_server when it's loaded (not when specs are run), I am setting `RUNNING_SPEC_SERVER=1` before running `script/spec_server -d`, then unsetting it afterwards. test.rb has `config.cache_classes = ENV['RUNNING_SPEC_SERVER'] != '1'` <div><p>Since the value of <code>config.cache_classes</code> only matters to spec_server when it's loaded (not when specs are run), I am setting <code>RUNNING_SPEC_SERVER=1</code> before running <code>script/spec_server -d</code>, then unsetting it afterwards.</p> <p>test.rb has <code>config.cache_classes = ENV['RUNNING_SPEC_SERVER'] != '1'</code></p></div> false 2009-04-02T20:12:58+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug 2009-04-02T20:13:03+02:00 12071 Mark Wilden Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I'm putting this ticket on hold. This means it will only be reopened and prioritized if someone comments on it. Please read this first: http://www.nabble.com/-Cucumber--Spring-cleaning-td22928488.html <div><p>I'm putting this ticket on hold. This means it will only be reopened and prioritized if someone comments on it. Please read this first: <a href="http://www.nabble.com/-Cucumber--Spring-cleaning-td22928488.html">http://www.nabble.com/-Cucumber-...</a></p></div> true 2009-04-07T16:00:07+02:00 12071 --- :tag: bug :state: open 165 error-when-not-caching-classes 0 16211 hold 2009-04-07T16:00:10+02:00 1302 Aslak Hellesøy Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Seems to be related to #284. Reopening. My question again: Would a separate config/environments/cucumber.rb be an acceptable fix for this? <div><p>Seems to be related to <a href="/projects/16211/tickets/284" title="Ticket #284">#284</a>. Reopening.</p> <p>My question again: Would a separate config/environments/cucumber.rb be an acceptable fix for this?</p></div> false 2009-04-19T22:51:51+02:00 12071 --- :tag: :state: hold 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-04-19T22:51:54+02:00 1302 Aslak Hellesøy Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 Here is a patch that will warn people about the bug when they try to use cache_classes=false with Cucumber's use_transactional_fixtures: http://github.com/bmabey/cucumber/commit/e9ba91b94f91956d8c010deb45e334659d47e097 <div><p>Here is a patch that will warn people about the bug when they try to use cache_classes=false with Cucumber's use_transactional_fixtures:</p> <p><a href="http://github.com/bmabey/cucumber/commit/e9ba91b94f91956d8c010deb45e334659d47e097"> http://github.com/bmabey/cucumbe...</a></p></div> false 2009-04-20T03:24:48+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-04-20T03:24:53+02:00 9748 Ben Mabey Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 The thought just occurred to me.. the reason why Cucumber blows up with classes reloading and RSpec doesn't is because RSpec relies on ActiveSupport::TestCase to do it's transactional fixtures. My guess is that when Cucumber fires the After hooks the classes have already been reloaded. Whereas with ActiveSupport::TestCase I'm sure the reloading of classes is timed well with the cleanup of fixtures. So to fix this problem we will need to see if we can run the After hooks before the reloading of the classes. Well.. assuming that my hypothesis is correct and that it is the root of the problem. :) Anyways, I just wanted to make a note of it before I forgot. :) I'll investigate it when I get some time, but if someone has some deeper insights into Rails' class reloading please share. <div><p>The thought just occurred to me.. the reason why Cucumber blows up with classes reloading and RSpec doesn't is because RSpec relies on ActiveSupport::TestCase to do it's transactional fixtures. My guess is that when Cucumber fires the After hooks the classes have already been reloaded. Whereas with ActiveSupport::TestCase I'm sure the reloading of classes is timed well with the cleanup of fixtures. So to fix this problem we will need to see if we can run the After hooks before the reloading of the classes. Well.. assuming that my hypothesis is correct and that it is the root of the problem. :) Anyways, I just wanted to make a note of it before I forgot. :) I'll investigate it when I get some time, but if someone has some deeper insights into Rails' class reloading please share.</p></div> false 2009-04-20T06:58:31+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-04-20T06:58:35+02:00 9748 Ben Mabey Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 I'm assigning this to you Ben - since you have started digging into the dark corners of Rails. <div><p>I'm assigning this to you Ben - since you have started digging into the dark corners of Rails.</p></div> false 2009-04-26T19:12:20+02:00 12071 --- :assigned_user: 1302 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-04-26T19:12:23+02:00 1302 Aslak Hellesøy Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 I don't think there is a clean and easy way of getting rail's cache_classes to work well with Cucumber. At Railsconf David and I added an IntegrationExampleGroup to RSpec and we found that rspec had similar issues with class reloading when using the integration session. The issue seems to be with rails and it's integration session.. which according to wycats will be deprecated in favor of rack test sometime anyways. There are a couple of workarounds we could do. One of them is have the generator create a new environment file for features as Aslak suggested. I think this is the best option and I vote we go with it. Does anyone else have any other suggestions before I implement it? Shall I call the new environment 'features' or 'cucumber'? I was thinking 'features' but don't have a strong opinion either way. <div><p>I don't think there is a clean and easy way of getting rail's cache_classes to work well with Cucumber.</p> <p>At Railsconf David and I added an IntegrationExampleGroup to RSpec and we found that rspec had similar issues with class reloading when using the integration session. The issue seems to be with rails and it's integration session.. which according to wycats will be deprecated in favor of rack test sometime anyways.</p> <p>There are a couple of workarounds we could do. One of them is have the generator create a new environment file for features as Aslak suggested. I think this is the best option and I vote we go with it.</p> <p>Does anyone else have any other suggestions before I implement it? Shall I call the new environment 'features' or 'cucumber'? I was thinking 'features' but don't have a strong opinion either way.</p></div> false 2009-05-20T00:59:11+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-20T00:59:15+02:00 9748 Ben Mabey Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 I think "cucumber" is better than "features" (I'll add a ticket for renaming the rake tasks from "features" to "cucumber" too...) <div><p>I think "cucumber" is better than "features"</p> <p>(I'll add a ticket for renaming the rake tasks from "features" to "cucumber" too...)</p></div> false 2009-05-20T01:01:03+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-20T01:01:04+02:00 1302 Aslak Hellesøy Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 I started adding a cucumber environment file in the cucumber's rails generator. However, I don't know how we should handle the database connection. Rails will try to use the 'cucumber' database connection. I've tried setting the connection :test within the cucumber.rb file but wiht no luck. I don't believe generators can modify arbitrary files (i.e. database.yml), or at least they shouldn't. ATM, my best idea is to print instructions when the generator is ran telling the user they need to add a cucumber entry in database.yml. Does that sound reasonable? <div><p>I started adding a cucumber environment file in the cucumber's rails generator. However, I don't know how we should handle the database connection. Rails will try to use the 'cucumber' database connection. I've tried setting the connection :test within the cucumber.rb file but wiht no luck. I don't believe generators can modify arbitrary files (i.e. database.yml), or at least they shouldn't.</p> <p>ATM, my best idea is to print instructions when the generator is ran telling the user they need to add a cucumber entry in database.yml. Does that sound reasonable?</p></div> false 2009-05-20T06:28:57+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-20T06:28:58+02:00 9748 Ben Mabey Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 Actually, you can modify files with some m.gsub_file in rails generators. For example, routes.rb is modified by a Rails generator. We also modify paths.rb in the feature generator. I think adding a cucumber sqlite3 entry is absolutely in order :-) <div><p>Actually, you can modify files with some m.gsub_file in rails<br> generators. For example, routes.rb is modified by a Rails generator.<br> We also modify paths.rb in the feature generator.</p> <p>I think adding a cucumber sqlite3 entry is absolutely in order :-)</p></div> false 2009-05-20T08:50:57+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-20T08:50:58+02:00 1302 Aslak Hellesøy Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 Thanks for the tip! Patch: http://github.com/bmabey/cucumber/commit/2220bd857349bbb4166106e017cdd25f4bede9bc You will need to regenerate the manifest and gemspec file to include the new file. When I tried I ran into this error: <pre> bmabey@BenzII:~/p/ruby/cucumber (master)$ rake manifest:refresh (in /Users/bmabey/Programming/ruby/cucumber) rm -r coverage rm -r pkg rm -r doc rm -r doc rm -r pkg rm -r coverage exclude entry missing from .hoerc. Aborting. patch: **** Only garbage was found in the patch input. </pre> <div><p>Thanks for the tip!</p> <p>Patch:</p> <p><a href= "http://github.com/bmabey/cucumber/commit/2220bd857349bbb4166106e017cdd25f4bede9bc"> http://github.com/bmabey/cucumber/commit/2220bd857349bbb4166106e017...</a></p> <p>You will need to regenerate the manifest and gemspec file to include the new file. When I tried I ran into this error:</p> <pre> bmabey@BenzII:~/p/ruby/cucumber (master)$ rake manifest:refresh (in /Users/bmabey/Programming/ruby/cucumber) rm -r coverage rm -r pkg rm -r doc rm -r doc rm -r pkg rm -r coverage exclude entry missing from .hoerc. Aborting. patch: **** Only garbage was found in the patch input. </pre></div> false 2009-05-21T06:23:27+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-21T06:23:32+02:00 9748 Ben Mabey Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 Oh, and to test this in cucumber_rails you will need this commit: http://github.com/bmabey/cucumber_rails/commit/684ca8b9aa9122f172e49813c0b47c46b9339e6d <div><p>Oh, and to test this in cucumber_rails you will need this commit:</p> <p><a href= "http://github.com/bmabey/cucumber_rails/commit/684ca8b9aa9122f172e49813c0b47c46b9339e6d"> http://github.com/bmabey/cucumber_rails/commit/684ca8b9aa9122f172e4...</a></p></div> false 2009-05-21T06:41:13+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-21T06:41:17+02:00 9748 Ben Mabey Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 Regarding the Hoe error: no idea. I can see one problem with introducing a new environment: @@@ # cucumber.rake task :features => 'db:test:prepare' @@@ This is there so that the test database is always set up before cucumber runs. With a new cucumber environment, preparing the test database has no effect. It would be nice if we could just change this to: @@@ # cucumber.rake task :features => 'db:cucumber:prepare' @@@ But unfortunately that's not possible - Rails hardcodes :test in their tasks :-/ So until there is a way around that (patching rails?) people have to remember to explicitly migrate their cucumber database before running features with rake. Don't you think a lot of people are going to forget this and run down the ML with questions? <div><p>Regarding the Hoe error: no idea.</p> <p>I can see one problem with introducing a new environment:</p> <pre> <code># cucumber.rake task :features =&gt; 'db:test:prepare'</code> </pre> <p>This is there so that the test database is always set up before cucumber runs. With a new cucumber environment, preparing the test database has no effect. It would be nice if we could just change this to:</p> <pre> <code># cucumber.rake task :features =&gt; 'db:cucumber:prepare'</code> </pre> <p>But unfortunately that's not possible - Rails hardcodes :test in their tasks :-/</p> <p>So until there is a way around that (patching rails?) people have to remember to explicitly migrate their cucumber database before running features with rake.</p> <p>Don't you think a lot of people are going to forget this and run down the ML with questions?</p></div> false 2009-05-22T11:49:55+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-22T11:49:58+02:00 1302 Aslak Hellesøy Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 I do see a barrage of complaints on the ML... here are some ideas... We could add our own db:cucumber:prepapre task. Or, we could use the test database in the cucumber environment. That would ensure the DB is cleaned. When people want to switch to a new DB they would have to work out how they want to handle the DB prepare tasks. To get the Cucumber env to use the test env DB I would just alias the test database yml block and use it in cucumber (i.e. test: &TEST). I vote for just using the test DB until a better solution (i.e. Rails doesn't hardcode test) is presented. <div><p>I do see a barrage of complaints on the ML... here are some ideas...</p> <p>We could add our own db:cucumber:prepapre task.<br></p> <p>Or, we could use the test database in the cucumber environment. That would ensure the DB is cleaned. When people want to switch to a new DB they would have to work out how they want to handle the DB prepare tasks. To get the Cucumber env to use the test env DB I would just alias the test database yml block and use it in cucumber (i.e. test: &amp;TEST).</p> <p>I vote for just using the test DB until a better solution (i.e. Rails doesn't hardcode test) is presented.</p></div> false 2009-05-22T16:38:24+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-22T16:38:29+02:00 9748 Ben Mabey Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 Per convo in IRC we went with using the test DB idea. Pull when you get a chance. <div><p>Per convo in IRC we went with using the test DB idea. Pull when you get a chance.</p></div> false 2009-05-22T17:00:57+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 open bug rails rollback transaction world 2009-05-22T17:01:03+02:00 9748 Ben Mabey Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 (from [2220bd857349bbb4166106e017cdd25f4bede9bc]) rails generator now generates a cucumber env to avoid potential cache_classes conflicts in test.rb [#165 state:resolved] http://github.com/aslakhellesoy/cucumber/commit/2220bd857349bbb4166106e017cdd25f4bede9bc <div><p>(from <a href= "/projects/16211/changesets/2220bd857349bbb4166106e017cdd25f4bede9bc" title= "Changeset [2220bd857349bbb4166106e017cdd25f4bede9bc]">[2220bd857349bbb4166106e017cdd25f4bede9bc]</a>) rails generator now generates a cucumber env to avoid potential cache_classes conflicts in test.rb [<a href= "/projects/16211/tickets/165" title="Ticket #165">#165</a> state:resolved]<br> <a href= "http://github.com/aslakhellesoy/cucumber/commit/2220bd857349bbb4166106e017cdd25f4bede9bc"> http://github.com/aslakhellesoy/cucumber/commit/2220bd857349bbb4166...</a></p></div> true 2009-05-22T20:19:39+02:00 12071 --- :state: open 165 error-when-not-caching-classes 0 16211 resolved bug rails rollback transaction world 2009-05-22T20:19:40+02:00 1302 Aslak Hellesøy Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 9748 0 (from [01d163dad1042cfb8370146c3408c9e3b9cfbdfb]) Rails generator creates a cucumber environment file to avoid potential cache_classes conflicts in test.rb [#165 state:resolved] http://github.com/aslakhellesoy/cucumber/commit/01d163dad1042cfb8370146c3408c9e3b9cfbdfb <div><p>(from <a href= "/projects/16211/changesets/01d163dad1042cfb8370146c3408c9e3b9cfbdfb" title= "Changeset [01d163dad1042cfb8370146c3408c9e3b9cfbdfb]">[01d163dad1042cfb8370146c3408c9e3b9cfbdfb]</a>) Rails generator creates a cucumber environment file to avoid potential cache_classes conflicts in test.rb [<a href= "/projects/16211/tickets/165" title="Ticket #165">#165</a> state:resolved] <a href= "http://github.com/aslakhellesoy/cucumber/commit/01d163dad1042cfb8370146c3408c9e3b9cfbdfb"> http://github.com/aslakhellesoy/cucumber/commit/01d163dad1042cfb837...</a></p></div> true 2009-05-22T20:19:40+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 resolved bug rails rollback transaction world 2009-05-22T20:19:41+02:00 1302 Aslak Hellesøy Mark Wilden Ben Mabey http://rspec.lighthouseapp.com/projects/16211/tickets/165 0 I had the same problem, so I read through all of this only to finally realize that my database table did not support transactions :-( Some of my tables were of type MyISAM (which don't support transactions) while others were InnoDB. All I had to to was change the table type from MyISAM to InnoDB and now it all works! I wanted to mention this, since undoubtedly others will find themselves in the same jam. <div><p>I had the same problem, so I read through all of this only to finally realize that my database table did not support transactions :-( Some of my tables were of type MyISAM (which don't support transactions) while others were InnoDB. All I had to to was change the table type from MyISAM to InnoDB and now it all works!</p> <p>I wanted to mention this, since undoubtedly others will find themselves in the same jam.</p></div> true 2009-07-09T07:38:32+02:00 12071 --- :tag: bug rails rollback transaction world :assigned_user: 9748 165 error-when-not-caching-classes 0 16211 resolved bug database innodb myisam rails rollback table transaction type world 2009-07-09T07:38:37+02:00 62273 Eivind Hagen Mark Wilden http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 I've read through all the comments here and would like to know if that now resolves the message I got when I started up spork for cucumber: @@@ $ spork cuc Using Cucumber Preloading Rails environment Loading Spork.prefork block... WARNING: You have set Rails' config.cache_classes to false (most likely in config/environments/test.rb). This setting is known to break Cucumber's use_transactional_fixtures method. Set config.cache_classes to true if you want to use transactional fixtures. For more information see https://rspec.lighthouseapp.com/projects/16211/tickets/165. Spork is ready and listening on 8990! @@@ Is this message now not relevant? (And shouldn't it be removed?) Also, I had cache_classes set to false because it was causing issues with spec_server, will things work correctly if I set it to true and am using spork? <div><p>I've read through all the comments here and would like to know if that now resolves the message I got when I started up spork for cucumber:</p> <pre> <code>$ spork cuc Using Cucumber Preloading Rails environment Loading Spork.prefork block... WARNING: You have set Rails' config.cache_classes to false (most likely in config/environments/test.rb). This setting is known to break Cucumber's use_transactional_fixtures method. Set config.cache_classes to true if you want to use transactional fixtures. For more information see https://rspec.lighthouseapp.com/projects/16211/tickets/165. Spork is ready and listening on 8990!</code> </pre> <p>Is this message now not relevant? (And shouldn't it be removed?) Also, I had cache_classes set to false because it was causing issues with spec_server, will things work correctly if I set it to true and am using spork?</p></div> true 2009-07-23T07:01:34+02:00 12071 --- :assigned_user: 165 error-when-not-caching-classes 0 16211 resolved bug database innodb myisam rails rollback table transaction type world 2009-07-23T07:01:37+02:00 63715 nbenes Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 spec_server needed config.cache_classes to be false. However it messes up Cucumber's ability to rollback transactions. I don't think that spork alleviates this problem, and it certainly would still be a problem when running Cucumber without spork so the message is still relevant IMO. The cucumber rails generator now sets up another rails environment file for this reason in case you want to not cache your classes with your other tests. <div><p>spec_server needed config.cache_classes to be false. However it messes up Cucumber's ability to rollback transactions. I don't think that spork alleviates this problem, and it certainly would still be a problem when running Cucumber without spork so the message is still relevant IMO. The cucumber rails generator now sets up another rails environment file for this reason in case you want to not cache your classes with your other tests.</p></div> true 2009-07-23T07:13:40+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 resolved bug database innodb myisam rails rollback table transaction type world 2009-07-23T07:13:46+02:00 9748 Ben Mabey Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165 1302 0 To throw fuel on the fire, yaml-linking the configurations for `test` and `cucumber` in the database config file breaks the standard rake tasks `rake db:create:all` and `rake db:drop:all` - with the error "Database example_test doesn't exist" this exists in such a way that chained rake tasks fail, and you can't continue. @@@ $ rake db:drop:all db:create:all db:migrate db:test:clone features spec Database example_test doesn't exist @@@ At that point execution stops. :( <div><p>To throw fuel on the fire, yaml-linking the configurations for <code>test</code> and <code>cucumber</code> in the database config file breaks the standard rake tasks <code>rake db:create:all</code> and <code>rake db:drop:all</code> - with the error "Database example_test doesn't exist" this exists in such a way that chained rake tasks fail, and you can't continue.</p> <pre> <code> $ rake db:drop:all db:create:all db:migrate db:test:clone features spec Database example_test doesn't exist</code> </pre> <p>At that point execution stops. :(</p></div> true 2009-08-04T15:35:08+02:00 12071 --- {} 165 error-when-not-caching-classes 0 16211 resolved bug database innodb myisam rails rollback table transaction type world 2009-08-04T15:35:15+02:00 1379 Lee Hambley Mark Wilden Aslak Hellesøy http://rspec.lighthouseapp.com/projects/16211/tickets/165