similar to: ActiveRecord::Relation#except and #only loses scope extensions

Hi all, I just submitted a patch to 2-3-stable on lighthouse and wanted to bring it to folks general attention. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/896-be-a-little-more-discerning-about-which-exceptions-to-handle My explanation is a bit long-winded, but here''s the motivation for the patch, as explained in the lighthouse ticket: Perhaps I should open

Hi everyone, I just created my first rails patch. It is a simple textile doc error requiring only a single word to be changed. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5779 I uploaded a .diff file. Not sure what to do now but lighthouse guide says I should ask on here for someone to take a look. Thank you for your time, fooledbyprimes Peoria, Illinois, USA --

In Rails 3 the only way to get for content captured with the content_for method in a view is to call yield from within a view. However, sometimes is it useful to get to this data from within a helper (for instance to provide a default value). Calling yield from within the helper method won''t work, and accessing the @_content_for variable directly is not encouraged. Proposed solution: add

Hello everyone, I''m new in contributing and i saw in the contributing-guides, that i have to write an email at this list. I hope, that''s the right place for this. If it''s not, i''M really sorry.. ;) Could someone please give me feedback about this lighthouse-ticket?

A Rails 2.3.9 app with Active Record or Memcache session store will never send the session ID cookie to a client if the client doesn''t send any HTTP cookies in its requests. Rails integration tests didn''t catch this because they always send the HTTP_COOKIE header, even if it''s empty. This is a huge bug, as it can break keeping sessions on sites which don''t set

class Brake scope :good, where(:quality => ''good'') end Brake.all.select &:nil? #=> works fine Brake.good.select &:nil? #=> FAILS Last statement fails because Brake.good.select is returning ActiveRecord::Relation and not an array. I have posted a detailed discussion on ticket #4589 .

Hi all. I''ve submitted a lighthouse ticket + patch so you can avoid having to repeatedly tell the subdomain method on ActionDispatch::Request how many elements your TLD has. https://rails.lighthouseapp.com/projects/8994/tickets/5215-configurable-tld_length-for-subdomains Any thoughts? Good idea, bad idea? Thanks, Simon -- You received this message because you are subscribed to the

I just posted this ticket in Lighthouse, but thought perhaps some discussion here would help point me in the right direction toward a solution. Here is a description of the problem (from the ticket - https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/6693-arel-union-does-not-support-order-or-limit) : > If we take two `ActiveRecord::Relations` and join them via `union`:

I just upgraded to 2.1 and attempted to log in to my application and when this line is reached in my login action: redirect_to(index_url) I get the error "wrong number of arguments (0 for 1)" [stack trace below]. Here''s my route: map.index ''index'', :controller => ''e_simply'', :action => ''index'' I found

Hello all, I just recently opened supplied a patch for ticket #4498 (https:// rails.lighthouseapp.com/projects/8994/tickets/4498-rails-loses- precision-when-deserializing-timestamps-from-postgresql). In short, the current microsecond calculation converts a rational to a float, then to an integer, occasionally causing rounding error. I''ve supplied a patch against 2-3-stable (should also

Hi all, There are two tickets in lighthouse that point to problems with the use of context() in RSpec: * conflict with JRuby: http://rspec.lighthouseapp.com/projects/5645/tickets/728 * request context() be deprecated http://rspec.lighthouseapp.com/projects/5645/tickets/713 As there are a lot of people (and libraries) that mix and match describe() and context(), I don''t plan to

Hi I''m trying to create a basic test management tool to organise the manual testing I have to do. I''m working on the results recording module and have a problem. Basically, I want each test result to belong to a test case, a test environment and a build. I want to make sure there''s no duplication of results with these 3 properties. If someone tries to enter a new test

Hello, I''ve got a problem with deserialization of AR "serialize" method (http://apidock.com/rails/ActiveRecord/Base/serialize/class) in my tests. It just gives me pure String instead of my data Array. Example: User > AR::Base serialize :roles, Array end Console: u = User.new u.roles = ["admin", "support"] u.save # => true User.first.roles # =>

Hello guys, I went into milestones page (https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones) and found out that Rails 2.3.6 was due Jan 15, 2010. Does it mean all tickets in that milestone should be cleared first? If so, then I would pay attention to clear tickets in that bucket first. Thank you, Prem Sichanugrist (sikachu) -- You received this message because you are

Hi, a couple of days ago I filed a ticket related to a problem with the to_xml ActiveRecord method. ( https://rails.lighthouseapp.com/projects/8994/tickets/3982-patch-solved-a-bug-that-prevented-xml-serialization-when-activerecord-attributes-contains-more-than-column-values ). I solved it by making to_xml to infere the type by means of a ruby-xml type conversion, using a Hash that was already

I posted a ticket to lighthouse: http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/595-deprecate-integrate_views Please put your comments and thoughts there, as that is the best place for that discussion. I wanted to make it more "visible" so it could get wide community participation in case there are folks who absolutely feel integrate_views is necessary (considering that we

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

This is mostly theoretical, but ... I''m starting to use lighthouse (http://llighthouseapp.com) for my projects at work. I''m organizing iterations as milestones and stories as tickets tagged to a milestone. Lighthouse offers an API so that you can write access the data in your account and write apps to process that data. I think you see where this is going. It seems to me that

I have a set of one-to-many relationships, nested 4 deep. In other words: table_A has_many table_B, table_B belongs_to table_A, has_many table C, table_C belongs_to table_B, has_many table D, table_D belongs_to table_C Now, I want to to find on table_A, based on criteria in table_D, and I want to paginate it. And I need fields from all four tables in the result set. Does anyone know

Hi everybody. Per http://rubyforge.org/pipermail/rspec-users/2007-November/004572.html, we''re going to be moving ticket tracking over to lighthouse. We''d like to get this rolling sooner than later, but we''re fairly well occupied getting ready for the 1.1 release and writing rspec books :) We''ve got the lighthouse account set up. The thing we need to do to