This project is archived and is in readonly mode.
Metal apps not being called
Reported by Caleb Perkins | June 15th, 2010 @ 08:41 PM
My metal apps are no longer being called in Rails 3 beta 4, when it worked fine in beta 3. To my understanding, Rails loads metal apps first and passes down control when they return an X-Cascade header. To demonstrate:
Allow the metal piece to run in isolation
require File.expand_path('../../../config/environment', FILE) unless defined?(Rails)
class Poller
def self.call(env)
raise "metal!"
....
end
end
class AuctionsController
def index
raise "not metal"
...
end
end
returns "not metal" when in beta 3 it would return metal. Is there a new way to use metal apps?
Comments and changes to this ticket
-
ctm June 18th, 2010 @ 05:17 AM
Ticket 4889 appears to be the same issue and has been assigned to wycats by DHH, so that suggests DHH thinks it's a bug. OTOH, railties-3.0.0.beta4/CHANGELOG has:
*Rails 3.0.0 [beta 4] (June 8th, 2010)* * Version bump * Removed Rails Metal [YK & JV].so I'm certainly not sure what's going on, and I have a metal app that I'd like to work after upgrading to beta 4.
-
Santiago Pastorino June 19th, 2010 @ 12:21 AM
- State changed from “new” to “invalid”
Metal was removed, you have an explaination of what to do on the commit message.
http://github.com/rails/rails/commit/ed34652d1aca148fea61c5309c1bd5...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Caleb Perkins
Jeremy Kemper