Hi all, I released a gem for IRB the other day and somebody sent me a screencast of it killing Rails:
http://screencast.com/t/k6Nlk8Q0Csy
(As an aside, I think screencasts are the coolest way to do a bug report.)
He has a Rails app running; he installs my gem; he restarts his server; he gets an error in one of the my_model_url methods, i.e., model_path(my_model) fails for him as a result of installing a gem which is only required in his .irbrc, and not anywhere in his application.
A little while back, before I put it all in a gem, I had a lot of code in my .irbrc, and I frequently would see "Constant already initialized" errors showing up in my Rails logs for constants that were only specified in my .irbrc and not used anywhere else.
Consequently I very much suspect Rails is somehow picking up people's .irbrc files in its load path, and I kinda suspect it's a bug. I'm going to see if I can fix it, but I just thought I'd check here first to see if anybody has any idea where it might be coming from. (I don't know a thing about the internals of the Rails load sequence yet.) Any and all help muchly appreciated.
Giles