Xapian exceptions "Key too long" during notmuch new

2010-09-07 Thread Rob Browning 
Michal Sojka  writes:

> please try the version from git. I do not have the problem you report
> with this message. It seems that it was fixed after 0.3.1 release in
>
> commit 7b78eb4af6e87532795d09bd82152002ab4a74b1

Indeed.  About 10 hours and 1.3M messages later, everything seems fine.

Thanks for the help.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: Xapian exceptions "Key too long" during notmuch new

2010-09-07 Thread Rob Browning 
Michal Sojka  writes:

> please try the version from git. I do not have the problem you report
> with this message. It seems that it was fixed after 0.3.1 release in
>
> commit 7b78eb4af6e87532795d09bd82152002ab4a74b1

Indeed.  About 10 hours and 1.3M messages later, everything seems fine.

Thanks for the help.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Xapian exceptions "Key too long" during notmuch new

2010-09-07 Thread Michal Sojka 
Hi Rob,

On Mon, 06 Sep 2010, Rob Browning wrote:
> Jameson Rollins  writes:
> 
> > Hey, Rob.  I've never seen this error before.  I wonder if these
> > messages have some really long header names?  If it's not too onerous,
> > can you find the messages where this occurred?  There's a verbose
> > option, that might be useful.
> >
> > jamie.
> 
> OK, it looks like this is the first message that caused the exception:
> ...
> References: 
>   at Virgin.Net>

please try the version from git. I do not have the problem you report
with this message. It seems that it was fixed after 0.3.1 release in

commit 7b78eb4af6e87532795d09bd82152002ab4a74b1
Author: Carl Worth 
Date:   Fri Jun 4 12:39:36 2010 -0700

Add support (and tests) for messages with really long message IDs.

-Michal

Re: Xapian exceptions "Key too long" during notmuch new

2010-09-07 Thread Michal Sojka 
Hi Rob,

On Mon, 06 Sep 2010, Rob Browning wrote:
> Jameson Rollins  writes:
> 
> > Hey, Rob.  I've never seen this error before.  I wonder if these
> > messages have some really long header names?  If it's not too onerous,
> > can you find the messages where this occurred?  There's a verbose
> > option, that might be useful.
> >
> > jamie.
> 
> OK, it looks like this is the first message that caused the exception:
> ...
> References: 
> 

please try the version from git. I do not have the problem you report
with this message. It seems that it was fixed after 0.3.1 release in

commit 7b78eb4af6e87532795d09bd82152002ab4a74b1
Author: Carl Worth 
Date:   Fri Jun 4 12:39:36 2010 -0700

Add support (and tests) for messages with really long message IDs.

-Michal

___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Rob Browning 
Jameson Rollins  writes:

> Hey, Rob.  I've never seen this error before.  I wonder if these
> messages have some really long header names?  If it's not too onerous,
> can you find the messages where this occurred?  There's a verbose
> option, that might be useful.
>
> jamie.

OK, it looks like this is the first message that caused the exception:

-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: bad-mail.txt
URL: 

-- next part --

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Rob Browning 
Jameson Rollins  writes:

> Hey, Rob.  I've never seen this error before.  I wonder if these
> messages have some really long header names?  If it's not too onerous,
> can you find the messages where this occurred?  There's a verbose
> option, that might be useful.
>
> jamie.

OK, it looks like this is the first message that caused the exception:

Return-Path: 
X-Original-To: r...@raven.defaultvalue.org
Delivered-To: r...@raven.defaultvalue.org
Received: from defaultvalue.org (omen.defaultvalue.org [192.168.1.1])
by raven.defaultvalue.org (Postfix) with ESMTP id D63A71D3018
for ; Thu, 30 Dec 2004 19:01:37 -0600 (CST)
Received: by defaultvalue.org (Postfix)
id A19A64176; Thu, 30 Dec 2004 18:34:22 -0600 (CST)
Delivered-To: r...@defaultvalue.org
Received: from lists.samba.org (dp.samba.org [66.70.73.150])
by defaultvalue.org (Postfix) with ESMTP id 6F2F3416F
for ; Thu, 30 Dec 2004 18:34:22 -0600 (CST)
Received: from dp.samba.org (localhost [127.0.0.1])
by lists.samba.org (Postfix) with ESMTP id 125E4163B82
for ; Fri, 31 Dec 2004 00:34:22 + (GMT)
X-Original-To: rs...@lists.samba.org
Delivered-To: rs...@lists.samba.org
Received: from binome.blorf.net (dsl3-63-249-88-2.cruzio.com [63.249.88.2])
by lists.samba.org (Postfix) with ESMTP id 80F70162BD9
for ; Fri, 31 Dec 2004 00:33:47 + (GMT)
Received: by binome.blorf.net (Postfix, from userid 1000)
id 950F1291E; Thu, 30 Dec 2004 16:33:46 -0800 (PST)
Date: Thu, 30 Dec 2004 16:33:46 -0800
From: Wayne Davison 
To: Stephen Schembri 
X-Gnus-Mail-Source: maildir:/home/rlb/incoming-mail/spool/new
Message-ID: <20041231003346.ga1...@blorf.net>
References: 

Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="jI8keyz6grp/JLjh"
Content-Disposition: inline
In-Reply-To: 

User-Agent: Mutt/1.5.6+20040907i
Cc: rs...@lists.samba.org
Subject: Re: Timeout Issues
X-BeenThere: rs...@lists.samba.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: rsync user list 
List-Unsubscribe: ,

List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,

Sender: rsync-bounces+rlb=defaultvalue@lists.samba.org
Errors-To: rsync-bounces+rlb=defaultvalue@lists.samba.org
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
raven.defaultvalue.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS 
autolearn=ham version=3.0.1
Lines: 64
Xref: trouble.defaultvalue.org rsync:6592


--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Dec 30, 2004 at 11:23:07PM -, Stephen Schembri wrote:
> By default the timeout value is supposed to be 60 according to io.c, but
> in loadparam.c it is stating a value of 0 - is this statement correct?

The comment in io.c says that the default select() timeout is 60 secs,
which is not the same as the default rsync timeout value (which is 0,
meaning that rsync doesn't timeout).

> If I declare a timeout value of "timeout=20" in the config file, the
> value is ignored and the value of 60 seconds is always used.

The attached patch should fix this.

> Hope you have a Happy New Year and most of all, keep up the excellent
> work.

Thanks!

..wayne..

--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="timeout.patch"

--- clientserver.c  8 Dec 2004 17:11:15 -   1.134
+++ clientserver.c  31 Dec 2004 00:24:07 -
@@ -43,6 +43,7 @@ extern int filesfrom_fd;
 extern int remote_protocol;
 extern int protocol_version;
 extern int io_timeout;
+extern int select_timeout;
 extern int orig_umask;
 extern int no_detach;
 extern int default_af_hint;
@@ -476,8 +477,11 @@ static int rsync_module(int f_in, int f_
exit_cleanup(RERR_UNSUPPORTED);
}
 
-   if (lp_timeout(i))
+   if (lp_timeout(i)) {
io_timeout = lp_timeout(i);
+   if (io_timeout && io_timeout < select_timeout)
+   select_timeout = io_timeout;
+   }
 
start_server(f_in, f_out, argc, argp);
 

--jI8keyz6grp/JLjh
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--jI8keyz6grp/JLjh--


-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
___
notmuch mailing list
notmuch@notmuchmail.org
ht

Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Jameson Rollins 
On Mon, 06 Sep 2010 12:44:45 -0500, Rob Browning  
wrote:
> After quite a bit of time (issues with offlineimap and large maildirs),
> I finally got the point where I could run notmuch new, and although it
> did finish, there were two errrors that I wanted to ask about.  Are
> these important?
> 
> $ notmuch new
> [...]
> A Xapian exception occurred adding message: Key too long: length was 370 
> bytes, maximum length of a key is 252 bytes.
> Error: A Xapian exception occurred. Halting processing.
> [...]
> A Xapian exception occurred adding message: Key too long: length was 269 
> bytes, maximum length of a key is 252 bytes.
> Error: A Xapian exception occurred. Halting processing.
> Processed 1373303 total files in 10h 47m 31s (35 files/sec.). 
> Added 1292042 new messages to the database.

Hey, Rob.  I've never seen this error before.  I wonder if these
messages have some really long header names?  If it's not too onerous,
can you find the messages where this occurred?  There's a verbose
option, that might be useful.

jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:

Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Rob Browning 
Jameson Rollins  writes:

> Hey, Rob.  I've never seen this error before.  I wonder if these
> messages have some really long header names?  If it's not too onerous,
> can you find the messages where this occurred?  There's a verbose
> option, that might be useful.

OK, if I remember, I'll recreate the index tonight.  BTW, it doesn't
look like --verbose is mentioned in the manpage.

Also, I think it may have been mentioned before, but it'd be nice if I
could tell new to write the index somewhere else so that I can keep
using notmuch while it's busy, i.e.

  notmuch new --verbose -o ~/new-notmuch-index

or similar.

Thanks for the help
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Rob Browning 

After quite a bit of time (issues with offlineimap and large maildirs),
I finally got the point where I could run notmuch new, and although it
did finish, there were two errrors that I wanted to ask about.  Are
these important?

$ notmuch new
[...]
A Xapian exception occurred adding message: Key too long: length was 370 bytes, 
maximum length of a key is 252 bytes.
Error: A Xapian exception occurred. Halting processing.
[...]
A Xapian exception occurred adding message: Key too long: length was 269 bytes, 
maximum length of a key is 252 bytes.
Error: A Xapian exception occurred. Halting processing.
Processed 1373303 total files in 10h 47m 31s (35 files/sec.). 
Added 1292042 new messages to the database.


Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Rob Browning 
Jameson Rollins  writes:

> Hey, Rob.  I've never seen this error before.  I wonder if these
> messages have some really long header names?  If it's not too onerous,
> can you find the messages where this occurred?  There's a verbose
> option, that might be useful.

OK, if I remember, I'll recreate the index tonight.  BTW, it doesn't
look like --verbose is mentioned in the manpage.

Also, I think it may have been mentioned before, but it'd be nice if I
could tell new to write the index somewhere else so that I can keep
using notmuch while it's busy, i.e.

  notmuch new --verbose -o ~/new-notmuch-index

or similar.

Thanks for the help
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Jameson Rollins 
On Mon, 06 Sep 2010 12:44:45 -0500, Rob Browning  wrote:
> After quite a bit of time (issues with offlineimap and large maildirs),
> I finally got the point where I could run notmuch new, and although it
> did finish, there were two errrors that I wanted to ask about.  Are
> these important?
> 
> $ notmuch new
> [...]
> A Xapian exception occurred adding message: Key too long: length was 370 
> bytes, maximum length of a key is 252 bytes.
> Error: A Xapian exception occurred. Halting processing.
> [...]
> A Xapian exception occurred adding message: Key too long: length was 269 
> bytes, maximum length of a key is 252 bytes.
> Error: A Xapian exception occurred. Halting processing.
> Processed 1373303 total files in 10h 47m 31s (35 files/sec.). 
> Added 1292042 new messages to the database.

Hey, Rob.  I've never seen this error before.  I wonder if these
messages have some really long header names?  If it's not too onerous,
can you find the messages where this occurred?  There's a verbose
option, that might be useful.

jamie.


pgpwHOnUWT1ii.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Xapian exceptions "Key too long" during notmuch new

2010-09-06 Thread Rob Browning 

After quite a bit of time (issues with offlineimap and large maildirs),
I finally got the point where I could run notmuch new, and although it
did finish, there were two errrors that I wanted to ask about.  Are
these important?

$ notmuch new
[...]
A Xapian exception occurred adding message: Key too long: length was 370 bytes, 
maximum length of a key is 252 bytes.
Error: A Xapian exception occurred. Halting processing.
[...]
A Xapian exception occurred adding message: Key too long: length was 269 bytes, 
maximum length of a key is 252 bytes.
Error: A Xapian exception occurred. Halting processing.
Processed 1373303 total files in 10h 47m 31s (35 files/sec.). 
Added 1292042 new messages to the database.


Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch