[sup-talk] Bug: Converting the index to xapian fails with a message with very old date

[William Morgan]

Reformatted excerpts from Michael Stapelberg's message of 2009-09-20:
> This makes sup/xapian/ruby (one of them) go crazy and abort with an exception:
> ## read 5856m (about 72%) @ 10.0m/s. 0:09:47 elapsed, about 0:03:44 remaining
> /usr/lib/ruby/1.8/sup/xapian_index.rb:532:in `_dump': year too big to marshal
> (ArgumentError)

Interesting. The Xapian index has had some trouble with crazy dates in
the past, but that should be fixed. Can you apply the following debug
patch and send the output for that message?

Thanks!

diff --git a/lib/sup/xapian_index.rb b/lib/sup/xapian_index.rb
index ab25ea0..b94c8b0 100644
--- a/lib/sup/xapian_index.rb
+++ b/lib/sup/xapian_index.rb
@@ -509,6 +509,9 @@ EOS
       Xapian.sortable_serialise 0
     end
 
+    puts "> truncated date is #{truncated_date.inspect}"
+    puts "> date_value is #{date_value.inspect}"
+
     docid = nil
     unless doc = find_doc(m.id)
       doc = Xapian::Document.new

-- 
William <wmorgan-sup at masanjin.net>