more verbose warning on boot failure
Reported by Roger | May 23rd, 2008 @ 06:45 PM
It would be helpful for at least a few people [myself included] if, when rails encounters a LoadError loading rubygems, it outputs what the error was.
In my instance someone was requiring, a few lines above, an added gem which I didn't have, however, the error was being swallowed up and blamed on a gem version [which wasn't the real cause].
This patch is simple and clears up any doubts for the user.
Comments and changes to this ticket
-
Roger May 23rd, 2008 @ 11:00 PM
here's the same patch using the approved git style patch instead of git diff.
To test this patch apply, then go to boot.rb and add
require 'nonexisting' within the
load_rubygems
method
You should see a more appropriately output error message than what it had been before.
-
Adam S May 24th, 2008 @ 01:15 PM
+1
Patch works and seems a reasonable change. I'm pretty sure I've had a similar issue where the LoadError that wasn't rubygems.
-
Joshua Peek July 17th, 2008 @ 01:56 AM
- → Tag changed from “” to “edge patch railties”
- → State changed from “new” to “resolved”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
