This project is archived and is in readonly mode.
[PATCH] Rails3 application named 'Test' fails webrick with uninitialized constant Rack::Test::Application
-
MOE
- Tag set to rails 3.0, rack, server, webrick
-
José Valim
Could you please provide a patch to update the docs then? Thanks.
-
Kieran P
It might be worth adding a check to see if the constant is already defined in the current app, i.e.
raise "Already used" if defined?(APP_NAME) -
José Valim
It's more complicated than that. In this case, it's failing due to Rack::Test. And defined?(Test) wouldn't get it.
-
Kieran P
- Title changed from Rails3 application named 'Test' fails webrick with uninitialized constant Rack::Test::Application to [PATCH] Rails3 application named 'Test' fails webrick with uninitialized constant Rack::Test::Application
Right, but checking to make sure things like String or Module aren't used would be a good start.
I've attached a patch +tests to do this.
-
ecleel
- Tag changed from rails 3.0, rack, server, webrick to rails 3.0, rack, server, thin
Thin webserver gives me same problem.
thin -v = 1.2.7
-
ecleel
- Tag changed from rails 3.0, rack, server, thin to rails 3.0, rack, server, thin, webrick
-
José Valim
- Milestone cleared.
- Assigned user set to José Valim
-
Repository
(from [9268b598bb20523e1b886f8811598647ce427ef9]) Add a check to ensure that the application name does not already exist, i.e. String or Module are part of ruby [#3872 [PATCH] Rails3 application named 'Test' fails webrick with uninitialized cons... status:resolved]
Signed-off-by: José Valim jose.valim@gmail.com
http://github.com/rails/rails/commit/9268b598bb20523e1b886f88115986...
