similar to: Mocha 0.5.6 breaks ActionController test

Hi all, I just submitted a patch that would allow you to pass a proc to ActionController::Base.asset_host rather than just using a %d wildcard (e.g. assets%d.example.com). Basically this frees you from the hard-coded assumption that you have 4 hosts numbered 0-3 and also allows you to do smarter things depending on the asset (e.g. images from a particular domain, stylesheets from another). The

Just a quick pointer to some ActiveSupport patches hoping for reviews: Puts Array#to_query and Object#to_query in the right places in ActiveSupport - http://dev.rubyonrails.org/ticket/10395 Preserve user-specified content type for XML and JSON rendering (currently it''s overridden and set to Mime::XML/Mimi::JSON - http://dev.rubyonrails.org/ticket/10388 Oh and a tiny patch for

I like the merb-style exception pages where there''re links to open the files listed in the stack trace in TextMate and the source around each line a lot so I stole the idea (and the code!) and made a patch for Rails: http://dev.rubyonrails.org/ticket/10401 Here''s how it looks like in Merb: http://yehudakatz.com/wp-content/uploads/stacktrace.gif What do you guys think?

Please check out this ticket (which would explain almost everything): http://dev.rubyonrails.org/ticket/8762 So basically, Rails to_json methods produces invalid JSON out of the box as it doesn''t quote all hash keys. This is valid JSON: { "id": 6589, "code": "SIN", "name": "Singapore" } This is not (Rails'' JSON encoders

I''d really like to see just 2 more functional changes to the JSON serialization/encoding before we get to Rails 2.0. First, and I think this is really crucial because without it all the efforts to output JSON from ActiveRecord objects would have been half in vain, is to allow us to do this in controllers: @authors = Author.find(:all) render :json => @authors.to_json(:only =>

Fix for the bad (failing) test here: http://dev.rubyonrails.org/ticket/10664 On Jan 2, 5:33 pm, alexey.verkhov...@gmail.com wrote: > The build failed. > > CHANGES > ------- > Revision 8522 committed by bitsweat on 2008-01-02 09:03:56 > db:sessions:clear task uses session_table_name method. Closes #10631 [Cheah Chu Yeow] > > M /trunk/railties/lib/tasks/databases.rake >

In case Rails 2.0 gets released without these bits of documentation regarding the recent JSON changes, I''d like to highlight some docfixes: http://dev.rubyonrails.org/ticket/9833 and http://dev.rubyonrails.org/ticket/9814 Could a committer could take a quick look? Thanks! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

Hi devs, I was trying to open a new ticket with a minor doc patch at the BackgroundDrb Trac (http://backgroundrb.devjavu.com/) and it seems like only admins have permission to do so. Is this intended? I read in the readme that patches should be mailed to this list, but I much prefer to use Trac since there''s already one set up. Any reason Trac is not open to registered Devjavu users?

I''m really glad the JSON changes got in, many thanks to all involved, committers and contributors alike :). But there''s still one feature that''s missing to achieve feature parity between the JSON and XML encoding/conversion. And that is the abililty to say in your controller: @authors = Author.find(:all) render :json => @authors.to_json(:only => :name)

Sorry for attaching patches in emails to the mailing list, but I''m still unable to login to Devjavu for Backgroundrb (I''m able to login just fine for Merb''s Devjavu and submitted a ticket successfully). Anyway, I encountered a bug when trying to #ask_status of a worker before it''s run (or rather, before its result_hash has been set to something). Not sure why

FYI - I''ve just released Mocha 0.5.6 to make Ruby 1.9 compatibility fixes available for those using released packages rather than subversion trunk. I''m not feeling well and so haven''t been able to test it other than by running all the tests using Ruby 1.9. Please let me know if you have any problems using it. Remember that it sometimes takes a while for a new gem

Hi, I''m getting a conflict between the Mocha plugin and the Rails SimplyHelpful plugin. For some reason the dom_id method from SimplyHelpful is not being found in my views when the Mocha plugin is installed. The dom_id method if used in the controller works properly. This is the error I get when running the tests: 1) Error: test_truth(HmmControllerTest):

Just some quick cleanup and documentation. Remove obsolete ActiveSupport::JSON::Variable - http://dev.rubyonrails.org/ticket/9969 Add documentation for Hash#to_json and Enumerable#to_json - http://dev.rubyonrails.org/ticket/9970 Please review :) Thanks! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

Hi guys, I''ve fixed a pretty annoying bug in Action caching that is detailed here: https://rails.lighthouseapp.com/projects/8994/tickets/6480-action-cache-filter-code-incorrectly-renders-nil-response-body-if-response-is-non-cacheable Would appreciate testers or a direct commit if it checks out :) Cheers, Chu Yeow -- You received this message because you are subscribed to the Google

Hi again everyone, I''ve 2 tiny doc patches mostly involving grammar fixes (and errant whitespace elimination). My English is not perfect so any review would be very welcome. The patches: http://dev.rubyonrails.org/ticket/9819 http://dev.rubyonrails.org/ticket/10062 Thanks! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you

Hi guys, I''m running mocha (0.3.2) against Rails core and just found an issue where the mock doesn''t go away after the test is run. For example: def test_reset_bang_doesn_reinstall_named_routes ActionController::Routing::Routes.named_routes.expects(:install).never @session.reset! end def test_zzz puts ActionController::Routing::Routes.named_routes.inspect

After installation of Mocha (0.9.7), running "script/spec spec" results in a "`const_missing'': uninitialized constant Test::Unit::TestResult::TestResultFailureSupport (NameError)" error. (As shown here; http://codepad.org/mTqztjwt ) I''m running Ruby 1.8.6 with Rails 2.3.4 on Windows, rspec (-rails) 1.2.8 (1.2.7.1), Test::Unit 2.0.3 As suggested roughly on

---------- Forwarded message ---------- From: noreply at rubyforge.org <noreply at rubyforge.org> Date: 11-Apr-2007 15:24 Subject: [ mocha-Bugs-5892 ] Using a setup method in test_case_class destroys subsequent test cases To: noreply at rubyforge.org Bugs item #5892, was opened at 2006-09-25 07:49 You can respond by visiting:

Begin forwarded message: > From: <noreply at rubyforge.org> > Date: 15 June 2007 10:44:07 BDT > To: noreply at rubyforge.org > Subject: [ mocha-Patches-11583 ] Mocha 0.5.0 throwing unexpected > warnings, one line patch included > > Patches item #11583, was opened at 2007-06-14 21:28 > You can respond by visiting: > http://rubyforge.org/tracker/? >

---------- Forwarded message ---------- From: Raymond O''connor <nappin713 at yahoo.com> Date: 23-Feb-2007 08:20 Subject: Re: Mocha test retry to connect up to 10 times To: ruby-talk ML <ruby-talk at ruby-lang.org> Hemant Kumar wrote: > On Fri, 2007-02-23 at 14:57 +0900, Raymond O''connor wrote: >> >> Any help would be greatly appreciated, thanks!