On Feb 22, 2011, at 1:52 PM, Ryan Davis wrote:
> I can't repro. I installed all the above versions and get:
> 
> 10016 % git log -n 1 --oneline
> 615a5cf Add failing test for the try_activate failure case of lazy 
> activation. Test is currently non-working I think due to util methodology
> 10017 % gitx
> 10018 % git log  C-c C-c
> 10018 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.b"); p 
> Gem.loaded_specs.keys.sort'
> ["rails"]
> 10019 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); p 
> Gem.loaded_specs.keys.sort'
> ["rails"]
> 
> I don't even see how an infinite loop is possible given that the real change 
> I made to Gem.activate was to remove the recursion.

Unknown, I can't repro either. I did this several times this morning. I am 
since running the latest master. Maybe it was an outlier or related to my 
irbrc. I'll keep an eye, but don't worry. Thanks for having a look.
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers

Reply via email to