From mboxrd@z Thu Jan  1 00:00:00 1970
From: rlane@club.cc.cmu.edu (Rich Lane)
Date: Fri, 02 Oct 2009 16:35:42 -0400
Subject: [sup-talk] Bug: Converting the index to xapian fails with a
	message with very old date
In-Reply-To: <1254404956-sup-6574@masanjin.net>
References: <1253475875-sup-5119@midna.zekjur.net>
	<1253973258-sup-3347@masanjin.net>
	<1254001080-sup-5742@midna.zekjur.net>
	<1254404956-sup-6574@masanjin.net>
Message-ID: <1254513417-sup-8419@zyrg.net>

Excerpts from William Morgan's message of Thu Oct 01 09:49:54 -0400 2009:
> Reformatted excerpts from Michael Stapelberg's message of 2009-09-26:
> > truncated date is Thu Jan 01 01:00:00 +0100 1970
> > date_value is "\200"
> > /usr/lib/ruby/1.8/sup/xapian_index.rb:536:in `_dump': year too big to marshal
> > (ArgumentError)
> >         from /usr/lib/ruby/1.8/sup/xapian_index.rb:536:in `dump'
> >         from /usr/lib/ruby/1.8/sup/xapian_index.rb:536:in `index_message'
> >         from /usr/lib/ruby/1.8/sup/xapian_index.rb:124:in `sync_message'
> 
> At this point I'm hoping that Rich will chime in. :)

This strikes me as a bug in Marshal.dump - it should be able to handle
arbitrary dates. I've never messed with custom marshalling functions
before, but monkey patching one in could be a workaround. Or we could
just truncate the dates before putting them in the index entry.