Spaceghost · January 2, 2014 03:23
diff --git a/gistfile1.txt b/gistfile1.txt
 01:15:52 <pipecloud> While working on getting rubygems.org to work on ruby 2.1 and 2.0, I've seem to hit a problem. the gem archives in test/gems/dos* are being used in test/unit/pusher_test.rb and they return StringIO objects. I've called #read on them prior to passing them Cutter.new, but I'm out of my understanding when they complain about "string contains null byte". I'm
 01:15:52 <pipecloud> curious about what I should change, but more curious about how they pass currently.
 01:16:58 <pipecloud> I'm going to be checking into 1.9.3 and seeing how it works there and hopefully that'll give me some more information. 
 01:24:00 <pipecloud> Where's sj26 when you need him? :(
 01:34:07 <pipecloud> I doubt it has anything to do with marshalling like in https://groups.google.com/forum/#!msg/ruby-core-google/eMLd2MgOnVU/OedFMqUOcuEJ which drbrain_ commented on, but I guess I'll keep digging.
	01:15:52 <pipecloud> While working on getting rubygems.org to work on ruby 2.1 and 2.0, I've seem to hit a problem. the gem archives in test/gems/dos* are being used in test/unit/pusher_test.rb and they return StringIO objects. I've called #read on them prior to passing them Cutter.new, but I'm out of my understanding when they complain about "string contains null byte". I'm
	01:15:52 <pipecloud> curious about what I should change, but more curious about how they pass currently.
	01:16:58 <pipecloud> I'm going to be checking into 1.9.3 and seeing how it works there and hopefully that'll give me some more information.
	01:24:00 <pipecloud> Where's sj26 when you need him? :(
	01:34:07 <pipecloud> I doubt it has anything to do with marshalling like in https://groups.google.com/forum/#!msg/ruby-core-google/eMLd2MgOnVU/OedFMqUOcuEJ which drbrain_ commented on, but I guess I'll keep digging.