From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Totally unrelated message shown in thread, sometimes
Date: Sat, 26 Dec 2020 11:30:51 -0800 [thread overview]
Message-ID: <871rfcuzys.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87czyw1wej.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Eric writes:
>
>> Does this only ever happen with delayed articles, or with other draft
>> articles, too?
>
> Now that you ask, I can only ever remember seeing my long-lived delayed
> article being mixed in.
>
> (I guess that points the suspicion towards the gnus-delay-send-queue
> demon-handler.)
>
>> Was drafting and delaying the outgoing article the last thing you did
>> before opening this group and seeing the fubar'ed headers? Or had you
>> delayed it a while ago?
>
> It is an old delayed article that I hadn't touched recently - it was
> last edited on October 4, 2020, and it's set to send on July 14, 2021.
>
>> And did you see the doubled headers on only one message in this group,
>> or for every message?
>
> Only in the one specific message shown on the screenshot.
>
>
> Eric writes:
>
>> I guess what I'm getting at with that last question is: is there any
>> chance that the article number of the delayed message in the delayed
>> group was the same as the article number of the article with doubled
>> headers in the feedbase group?
>
> I suspected that too, but the delayed article is ~/News/drafts/delayed/2
> while the article from f.b.risks has this Xref header:
>
> Xref: feedbase.org feedbase.blog.risks:6131
Okay, thanks for all data points!
> Anyway, given how rarely it happens and that it seems network
> instability is "needed", I guess it isn't worth too much time to chase
> down.
The bug itself isn't too bad, but understanding why it's happening might
lead to fixes for other stuff.
prev parent reply other threads:[~2020-12-26 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 7:45 Pankaj Jangid
2020-11-25 9:21 ` Adam Sjøgren
2020-11-25 10:08 ` Pankaj Jangid
2020-11-25 17:07 ` Eric Abrahamsen
2020-11-25 17:32 ` Adam Sjøgren
2020-11-25 17:40 ` Eric Abrahamsen
[not found] ` <87d001nenj.fsf@ust.hk>
[not found] ` <87k0u8zdv8.fsf@tullinup.koldfront.dk>
[not found] ` <87pn3zkfos.fsf@ucl.ac.uk>
2020-12-25 23:40 ` Adam Sjøgren
2020-12-26 5:54 ` Eric Abrahamsen
2020-12-26 5:58 ` Eric Abrahamsen
2020-12-26 14:20 ` Adam Sjøgren
2020-12-26 19:30 ` Eric Abrahamsen [this message]
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=871rfcuzys.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).