<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Rails: terminate called after throwing an instance of &#039;int&#039;</title>
	<atom:link href="http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/</link>
	<description>extraterrestrialicious web apps</description>
	<lastBuildDate>Tue, 27 Dec 2011 18:32:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Doug Daniels</title>
		<link>http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/comment-page-1/#comment-45</link>
		<dc:creator>Doug Daniels</dc:creator>
		<pubDate>Thu, 31 Jan 2008 16:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/#comment-45</guid>
		<description>I posted fix for this issue at http://cricketsinperil.com/2008/01/31/stricter-validation-for-rails-attachment_fu-plugin/

It uses the Unix file command to sniff the uploaded file, ensuring that it&#039;s really an allowed content type.  Might work for you if you&#039;re on a Unix-like platform.</description>
		<content:encoded><![CDATA[<p>I posted fix for this issue at <a href="http://cricketsinperil.com/2008/01/31/stricter-validation-for-rails-attachment_fu-plugin/" rel="nofollow">http://cricketsinperil.com/2008/01/31/stricter-validation-for-rails-attachment_fu-plugin/</a></p>
<p>It uses the Unix file command to sniff the uploaded file, ensuring that it&#8217;s really an allowed content type.  Might work for you if you&#8217;re on a Unix-like platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crickets in peril &#187; Blog Archive &#187; Stricter validation for Rails attachment_fu plugin</title>
		<link>http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/comment-page-1/#comment-44</link>
		<dc:creator>crickets in peril &#187; Blog Archive &#187; Stricter validation for Rails attachment_fu plugin</dc:creator>
		<pubDate>Thu, 31 Jan 2008 16:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/#comment-44</guid>
		<description>[...] version 1.1.3 gets very unhappy when asked to resize a file that isn&#8217;t an image. As mentioned here, if you pass ImageScience a simple ASCII text file, it will unceremoniously abort your Ruby [...]</description>
		<content:encoded><![CDATA[<p>[...] version 1.1.3 gets very unhappy when asked to resize a file that isn&#8217;t an image. As mentioned here, if you pass ImageScience a simple ASCII text file, it will unceremoniously abort your Ruby [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/comment-page-1/#comment-43</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Wed, 21 Nov 2007 00:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacebabies.nl/2007/10/19/rails-terminate-called-after-throwing-an-instance-of-int/#comment-43</guid>
		<description>I had the exact same problem today! I was writing tests for my app and created an invalid image scenario (on purpose), just hacked up a binary file and renamed it to a jpg. ImageScience 1.1.3 does cause this error to happen.

On the other hand, I will say that ImageScience is way faster and leaner than ImageMagick, which, after years of use, I now shy away from due to memory leaks, etc.</description>
		<content:encoded><![CDATA[<p>I had the exact same problem today! I was writing tests for my app and created an invalid image scenario (on purpose), just hacked up a binary file and renamed it to a jpg. ImageScience 1.1.3 does cause this error to happen.</p>
<p>On the other hand, I will say that ImageScience is way faster and leaner than ImageMagick, which, after years of use, I now shy away from due to memory leaks, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

