rails 2.3.3 problem ’ApplicationController removed from tree but still active ’ about authlogic

rails 2.3.3 problem ’ApplicationController removed from tree but still active ’

I used git bisect to locate the change within rails, and it looks like its the following change. Ben, can you judge if this is really authlogic fault or not? I think you just trigger it...

bc2c4a45959be21e6314fba7876b32c1f04cd08a is first bad commit
commit bc2c4a45959be21e6314fba7876b32c1f04cd08a
Author: Hongli Lai (Phusion) [email protected]
Date: Mon Jul 6 14:11:28 2009 +0200

Cleanup application after #close has been called on the Rack response body, not when AC::Reload#call is done.

The Rack body might lazily evaluate its output, which is for example the case
if one calls ’render :text => lambda { ... }’. The code which lazily evaluates
the output might use other application classes. So we will want to defer
cleanup until the Rack request is completely finished.

Signed-off-by: Michael Koziarski <[email protected]>

:040000 040000 da0577aae05718551970c1f4d3c6052bee64216a a75eb4b4b08fa3d5c6a25288590d4973b578d052 M actionpack

by Reto

rails 2.3.3 problem ’ApplicationController removed from tree but still active ’

Alright, looking for this commit id revealed the following two lighthouse tickets:

• https://rails.lighthouseapp.com/projects/8994/tickets/2873-application-reloading-should-be-deferred-to-end-of-request-currently-interferes-with-render-text-lambda-streaming
• https://rails.lighthouseapp.com/projects/8994/tickets/2948-exception-a-copy-of-actorscontroller-has-been-removed-from-the-module-tree-but-is-still-active

Which in turn shows to be fixed in http://github.com/rails/rails/commit/d37ac7958fc88fdbf37a8948102f6b4e45c530b3.

Hmm, I think you can close this bug.. but I fear for me 2.3.3 is broken :(.

by Reto