Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Partial IMAP article fetch
Date: Wed, 29 Sep 2010 21:16:19 +0200	[thread overview]
Message-ID: <87hbh8pdh8.fsf@dod.no> (raw)
In-Reply-To: <m34od8jrrk.fsf@quimbies.gnus.org>

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> Steinar Bang <sb@dod.no> writes:
>> It doesn't crash for me anymore on the LinkedIn article, but what shows
>> up in the *Article* buffer is this:
>> 
>> 7169	LinkedIn Network Updates, 9/28/2010 	LinkedIn Updates <updates@linkedin.com> 	Tue, 28 Sep 2010 07:40:57 -0700 (PDT) 	<213149815.58720010.1285684857650.JavaMail.app@ech3-cdn43.prod>		16003	69		Id: 	Ip: 	Queue: 	
>> pp

> That's bizarre.  That's a NOV line, and not an article.

> I think this has to be a separate issue of something invalid ending up
> in your Agent files, and not related to the partial fetch...

Indeed.  The last 4 articles in the agent consisted of NOV lines of
different length.  Two with approximate the contents of the .overview
files, one with a few NOV lines, and this last one with just the NOV
line for that particular article.

I've seen it before.

I cleaned out the b0rken agent files, and visit the article again, and
this time it opened.

However, I forwarded the article I thought had the problem to you, with
a BCC to myself, and the BCC'd articles gets the following stack trace
when trying to open:

Debugger entered--Lisp error: (wrong-type-argument listp NIL)
  nnimap-insert-partial-structure((("text" "plain" ("charset" "iso-8859-1") NIL NIL "quoted-printable" 57 2 NIL "1" NIL NIL) ("message" "rfc822" NIL NIL NIL "7bit" 16383 ("Tue, 28 Sep 2010 07:40:57 -0700 (PDT)" "LinkedIn Network Updates, 9/28/2010" ... ... ... ... NIL NIL NIL "<213149815.58720010.1285684857650.JavaMail.app@ech3-cdn43.prod>") (... ... "alternative" ... NIL NIL NIL) "2" NIL ("inline" NIL) NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL) (("1" "Her er problemartikkelen jeg nevnte p=E5 gnus-gruppa:\n\n")))
  nnimap-convert-partial-article((("text" "plain" ("charset" "iso-8859-1") NIL NIL "quoted-printable" 57 2 NIL "1" NIL NIL) ("message" "rfc822" NIL NIL NIL "7bit" 16383 ("Tue, 28 Sep 2010 07:40:57 -0700 (PDT)" "LinkedIn Network Updates, 9/28/2010" ... ... ... ... NIL NIL NIL "<213149815.58720010.1285684857650.JavaMail.app@ech3-cdn43.prod>") (... ... "alternative" ... NIL NIL NIL) "2" NIL ("inline" NIL) NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL))
  nnimap-get-partial-article(7192 ("1") (("text" "plain" ("charset" "iso-8859-1") NIL NIL "quoted-printable" 57 2 NIL "1" NIL NIL) ("message" "rfc822" NIL NIL NIL "7bit" 16383 ("Tue, 28 Sep 2010 07:40:57 -0700 (PDT)" "LinkedIn Network Updates, 9/28/2010" ... ... ... ... NIL NIL NIL "<213149815.58720010.1285684857650.JavaMail.app@ech3-cdn43.prod>") (... ... "alternative" ... NIL NIL NIL) "2" NIL ("inline" NIL) NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL))
  nnimap-request-article(7192 "dod" "privat" #<buffer *Article nnimap+privat:dod*>)
  gnus-request-article(7192 "nnimap+privat:dod" #<buffer *Article nnimap+privat:dod*>)
  gnus-request-article-this-buffer(7192 "nnimap+privat:dod")
  gnus-article-prepare(7192 nil)
  gnus-summary-display-article(7192 nil)
  gnus-summary-select-article(nil nil pseudo)
  gnus-summary-scroll-up(1)
  call-interactively(gnus-summary-scroll-up)







  reply	other threads:[~2010-09-29 19:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 16:12 Lars Magne Ingebrigtsen
2010-09-25 17:11 ` Lars Magne Ingebrigtsen
2010-09-26 20:41 ` Dan Christensen
2010-09-27 18:27   ` Lars Magne Ingebrigtsen
2010-09-27 18:45     ` Dan Christensen
2010-09-27 18:49       ` Dan Christensen
2010-09-27 19:25         ` Lars Magne Ingebrigtsen
2010-09-28  1:18           ` Dan Christensen
2010-09-28 16:05             ` Steinar Bang
2010-09-28 16:14               ` Steinar Bang
2010-09-28 16:16               ` Julien Danjou
2010-09-29 14:56                 ` Lars Magne Ingebrigtsen
2010-09-29 17:58                   ` Steinar Bang
2010-09-29 19:04                     ` Lars Magne Ingebrigtsen
2010-09-29 19:16                       ` Steinar Bang [this message]
2010-09-29 19:30                         ` Lars Magne Ingebrigtsen
2010-09-29 19:55                           ` Steinar Bang
2010-09-29 20:12                             ` Lars Magne Ingebrigtsen
2010-09-29 20:24                               ` Steinar Bang
2010-09-29 22:10                                 ` Lars Magne Ingebrigtsen
2010-09-29 22:11                                 ` Lars Magne Ingebrigtsen
2010-09-29 22:15                                   ` Lars Magne Ingebrigtsen
2010-09-30 18:42                                     ` Steinar Bang
2010-09-29 21:21                           ` Andreas Schwab
2010-09-29 21:23                             ` Lars Magne Ingebrigtsen
2010-09-29 22:45                               ` Andreas Schwab
2010-09-29 18:43                   ` Julien Danjou
2010-09-29 18:59                     ` Lars Magne Ingebrigtsen
2010-09-26 20:45 ` Dan Christensen
2010-09-26 20:55   ` Lars Magne Ingebrigtsen
2010-09-27  7:43   ` Steinar Bang
2010-09-27 18:35     ` Lars Magne Ingebrigtsen
2010-09-27 15:19   ` Richard Riley
2010-09-27 18:35     ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hbh8pdh8.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).