Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
larch
Home
+ new post
About this group
Join this group
Message from discussion Can't get larch 1.1.0
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ryan Grove  
View profile  
 More options Oct 26 2009, 9:12 pm
From: Ryan Grove <r...@wonko.com>
Date: Mon, 26 Oct 2009 18:12:11 -0700
Local: Mon, Oct 26 2009 9:12 pm
Subject: Re: Can't get larch 1.1.0
Print | View thread | Show original | Report this message | Find messages by this author

On Sun, Oct 25, 2009 at 8:28 PM, sidney <sidn...@gmail.com> wrote:
> I had to close the GMail tab to get to stop the repeating error, then
> I searched for the date range again and changed the label of the
> message to a new one I created. Now that is the only mail message in
> that folder and clicking on it to display it still produces the error.

> It certainly seems like Google's problem. Would a correct workaround
> be for Larch to ignore the error, missing just the one email, given
> that all the other headers do fetch ok?

Thanks for the additional analysis and details. Given what you've
described, it does seem like the best thing for Larch to do is to
ignore messages that trigger this error. The hard part, though, is
identifying them. When Larch scans headers in a folder, it does a
batch fetch of up to 1024 headers at a time, and the entire batch will
fail with this error if just one of the messages is corrupt. In order
to find the corrupt message, Larch would have to gradually decrease
the size of the batch until the fetch succeeds and the culprit is
identified, which could take a while.

Still, it'd be better for Larch to work around the problem slowly than
not work around it at all, so this is probably what I'll implement.

The only blocker now is that I'll need to be able to reproduce the
problem myself before I can test a solution for it. I don't currently
have any Gmail test mailboxes that are experiencing this problem, and
I haven't yet figured out a way to intentionally create a corrupt
message that will trigger it.

I don't suppose you'd be willing to try forwarding me your corrupt
message? Not sure if it'll even be possible if the web UI chokes on
the message, but it's worth a shot. Of course, I'll understand if
you'd prefer not to for privacy reasons.

- Ryan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google