similar to: [PATCH] ActiveSupport::OrderedHash#update Does Not Set Keys

I noticed that ActiveSupport::OrderedHash disappeared from the Rails API pages. Does it mean that it is going to be deprecated? I know that Hash is ordered in Ruby 1.9, but this subject seems controversial, and in my opinion the ordered hash in Ruby 1.9 should have been called OrderedHash (or SequentialHash), even if it be an alias of the current implementation of Hash. That way one would be free

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients. * http://unicorn.bogomips.org/ * mongrel-unicorn at

I understand that ActiveSupport::OrderedHash.new [[1,2]] does not work beginning with Rails 2.3. I am running Rails 2.3.2. One commentator suggested simply creating the instance without arguments and then sequentially adding each element as a separate step. I tried that. The hash gets populated just fine but it is not ordered. Can anyone please tell me what the magic trick is under

Looks like I have skipped on this, but still - a couple of questions: 1) Why there suddenly is an OrderedHash in ActiveSupport? (this glaring omission from ruby core is present in many apps already) 2) Why it doesn''t match the semantics of Hash respectively? 3) Why it''s #nodoc ? -- Julian ''Julik'' Tarkhanov please send all personal mail to me at julik.nl

Details/patch are in this lighthous ticket: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4172-inconsistency-with-cattr_readermattr_reader -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to

Hi I must be slipping, but say I have a string that looks like: 3/11/2012 2:50:00 AM If I use the UTC timezone and ask it to parse this time, what would you expect the result to be? Personally, I''d say 3/11/2012 2:50:00 AM UTC Given this is the DST switchover date (for some places) this is an edge case. It''s the "spring forward" rule so 2:50 AM is 3:50... But

Hi all, I wanted to draw some attention to a couple of very small multibyte-related patches I believe should be included before Rails 3.0 RC1: * Use String#bytesize rather than String#length in exception templates: This is a simple case where string length is checked, but bytes is needed, so it breaks with string with multibyte chars.

Hi all, I''ve created and submitted a patch to resolve an issue I had while attempting to meet the OpenSocial API specifications, which dictates that the xml output have tags formatted as lower camelcase (as opposed to upper camelcase, which is currently the only option). With this patch, simply passing :camelize => true still begets the current behavior, but you can now enable lower

Hi, when trying to migrate Signal to Rails 3 I tried to use the shorthand route for: match ''/projects/status(.:format)'' but it thrown an error because the controller was not specified. This happend because actually the shorthand routes only work with routes without optional parameters. The modification to support routes ending with a optional parameters is very simple, as can

I''ve submitted a couple of patches in Ligththouse. Provide NoStore implementation of ActiveSupport::Cache::Store This patch provides a NoStore implementation of ActiveSupport::Cache::Store suitable for use in development and test environments where the code need to use the cache interface, but actually caching data is not desired.

The way Rails handles root nodes in JSON and XML serialization is inconsistent. This has been discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/2584-232-activeresource-json-doesnt-send-parameters-with-root-node This seems mostly taken care of with ActiveModel::Base.include_root_in_json, especially if/when it ends up in ActiveResource. However, there is also the issue of how

Hello. Some time ago I committed a Rubinius assembly-based HTTP parser generated from Ragel to the Rubinius git repository. Yesterday I made a Mongrel gem which installs and works on Rubinius. This basically involved commenting out anything to do with fastthread or the http11 C extension. If there''s interest in releasing a Rubinius-targeted gem, I can make changes to the Rakefile to

Hi all, I''ve just pushed out some changes to the C HTTP parser that should make it compatible with a recent Rubinius[1] using the C API. While I got the http_parser and http_parser_ng tests to pass with the new changes, most of the other tests that use pure Ruby actually failed(!). If anybody wants to pick up where I left off (even if it''s to properly report bugs to the

Hi, I noticed that 2 days ago that this ticket was marked "stale". https://rails.lighthouseapp.com/projects/8994/tickets/6171 But the issue is still here (I checked just now), and it reminded me I had a patch for it I forgot to submit, so I attached the patch file to the ticket. Since I''m still new on this, can someone please point me the right procedure ? Should I have

Hello! Could someone review the patch attached to [1] and provide feedback? Briefly, it targets rails 3, and fixes "rails g model admin/post". The generated migration creates a "admin_posts" table while the model expects a table simply named "posts". With the patch, the migration creates "posts". Thank you! --phil-- [1]

Can somebody please review my ticket: https://rails.lighthouseapp.com/projects/8994/tickets/4879 It''s a trivial bugfix ("option_groups_from_collection_for_select should produce an HTML-safe string") before RC, I think. Cheers, Wincent -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group,

I believe I have fixed the issue Trever noted with has_one (http://rails.lighthouseapp.com/projects/8994/tickets/64-eager-loading-inconsistency ) if people would like o have a look. Fred --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Hi I''ve contributed a patch which fixes an incorrect example in the documentation for auto_link in ActionView::Helpers::TextHelper. The example uses truncate in the old style of tuncate(text, length) which no longer works, so I''ve patched it to use the new tuncate(text, :length => n) style.

I am having a problem with a belongs_to and a has_one :through relation which I found is a known bug in Ruby on Rails: http://rails.lighthouseapp.com/projects/8994/tickets/323-has_many-through-belongs_to_association-bug This ticket has 6 different attachments. Do I need all of them, or just the latest one? I can''t seem to find anywhere how one is supposed to deploy these patches.

This patch fixes an issue with protected methods becoming public if they are memoized. Looking for +1''s and/or a commit by core... https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5695 Thanks. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to