# Interrupt during require\_gem

**URL:** <https://www.ruby-forum.com/t/interrupt-during-require-gem/139323>\
**Category:** Ruby\
**Created:** [June 2, 2008, 10:44pm UTC](https://www.ruby-forum.com/t/interrupt-during-require-gem/139323 "2008-06-02T22:44:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joel\_VanderWerf](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@Joel\_VanderWerf](https://www.ruby-forum.com/u/Joel_VanderWerf)\
**Post date:** [June 2, 2008, 10:44pm UTC](https://www.ruby-forum.com/t/interrupt-during-require-gem/139323/1 "2008-06-02T22:44:22Z")

</div>

Bad timing I guess: I happened to interrupt a program presumably during  
require\_gem or whatever method happens when you have RUBYOPT=rubygems.  
This caused a huge dump of warnings about invalid gem specs (not even  
gems I was using in my code). Could this be handled in a way that  
doesn’t dump all these messages (shown below)? I’m not including the  
backtrace, because it didn’t show where these warnings were generated.

WARNING: Interrupt  
Gem::Specification.new do |s|  
s.name = %q{columnize}  
s.version = “0.1”

s.specification\_version = 1 if s.respond\_to? :specification\_version=

s.required\_rubygems\_version = nil if s.respond\_to?  
:required\_rubygems\_version=  
s.authors = [“R. Bernstein”]  
s.cert\_chain = nil  
s.date = %q{2007-12-08}  
s.description = %q{Columnize is a module for reading and caching  
lines. This may be useful for example in a debugger where the same lines  
are shown many times.}  
s.email = %q{removed\_email\_address@domain.invalid}  
s.extra\_rdoc\_files = [“README”, “lib/columnize.rb”]  
s.files = [“AUTHORS”, “COPYING”, “ChangeLog”, “NEWS”, “README”,  
“Rakefile”, “VERSION”, “lib/columnize.rb”, “test/test-columnize.rb”]  
s.has\_rdoc = true  
s.homepage = %q{[http://rubyforge.org/projects/rocky-hacks/columnize](http://rubyforge.org/projects/rocky-hacks/columnize)}  
s.require\_paths = [“lib”]  
s.required\_ruby\_version = Gem::Requirement.new(“\>= 1.8.2”)  
s.rubyforge\_project = %q{rocky-hacks}  
s.rubygems\_version = %q{1.1.0}  
s.summary = %q{Read file with caching}  
end  
WARNING: Invalid .gemspec format in  
‘/usr/local/lib/ruby/gems/1.8/specifications/columnize-0.1.gemspec’  
WARNING: Interrupt  
Gem::Specification.new do |s|  
s.name = %q{mongrel}  
s.version = “1.1.4”

s.specification\_version = 2 if s.respond\_to? :specification\_version=

…  
…

(and much more like this)

---

<div class="post-metadata">

**Author:** ![Joel\_VanderWerf](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@Joel\_VanderWerf](https://www.ruby-forum.com/u/Joel_VanderWerf)\
**Post date:** [June 3, 2008, 6:00am UTC](https://www.ruby-forum.com/t/interrupt-during-require-gem/139323/2 "2008-06-03T06:00:33Z")

</div>

> WARNING: Interrupt  
> Gem::Specification.new do |s|

I get those all the time, too, if I interrupt a rails app right after  
startup. Usually they’re considered benign, but, as you mentioned,  
confusing 🙂  
-R

---

<div class="post-metadata">

**Author:** ![Joel\_VanderWerf](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@Joel\_VanderWerf](https://www.ruby-forum.com/u/Joel_VanderWerf)\
**Post date:** [June 5, 2008, 6:42am UTC](https://www.ruby-forum.com/t/interrupt-during-require-gem/139323/3 "2008-06-05T06:42:40Z")

</div>

On Jun 2, 2008, at 13:42 PM, Joel VanderWerf wrote:

> s.name = %q{columnize}  
> lines. This may be useful for example in a debugger where the same  
> s.rubygems\_version = %q{1.1.0}
> 
> …  
> …
> 
> (and much more like this)

Can you file a bug? I know where to fix this, but am on a larger  
change at the moment and don’t want to confuse myself.

---

<div class="post-metadata">

**Author:** ![Joel\_VanderWerf](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e19b73/32.png) [@Joel\_VanderWerf](https://www.ruby-forum.com/u/Joel_VanderWerf)\
**Post date:** [June 5, 2008, 8:31am UTC](https://www.ruby-forum.com/t/interrupt-during-require-gem/139323/4 "2008-06-05T08:31:51Z")

</div>

Eric H. wrote:

> Can you file a bug? I know where to fix this, but am on a larger change  
> at the moment and don’t want to confuse myself.

Hi, Eric,  
Bug filed. Thanks!