Two messages merged into one

Jaimie

First 'get latest' in 0.78.2, I found two messages which were merged from two other messages.
I've checked in another newsreader from the same server, and they're not merged up there.

Top message:
Message-ID: <85494704-5a96-49a6-bfe1-55a3d17029f0n@googlegroups.com>

Bottom message: Message-ID: <qDo6Gy.15rE@kithrup.com> but oddly this is the one whose name is in the Messages pane, Dorothy.

Jaimie

And the second one,

Top message Message-ID: <ef8e5046-0d36-4e25-ae5c-3befd50bf5ddo@googlegroups.com>
Bottom one Message-ID: <qDo6Dy.15q3@kithrup.com>. Again this is the one whose name shows in the message list.

Andre

That is strange.
I subscribed the same newsgroup and I don't see that behaviour here.

1) What happens if you restart Usenapp?
2) Try selecting the message and choose "Download" (or CMD-D) from the context menu and see what happens. This will re-download the message.

Andre

BTW. Can you email/update the screenshot in the other discussion:
https://www.usenapp.com/forum/d/186-threading-pane-broken-big-sur

Thanks.

Jaimie

Ah. Actually more than two of these - a whole bunch of messages have done that. Want me to send any database files or anything?
Ah, crossposted. Will try those.

Andre

1) What happens if you restart Usenapp?
2) Try selecting such a message and choose "Download" (or CMD-D) from the context menu and see what happens. This will re-download the message.

Jaimie

Still showing merged after a restart.
Right-click Download doesn't affect it - there's a momentary "Downloading message" status bar update.

The DB is only 17meg, I'll mail you a link to a zip.

Jaimie

Ah! After doing the cmd-D, I need to step away from the post then come back to it. You need to add a 'refresh' after the download 🙂

That does seem to fix it. I do have the broken DB if you want it, from before the cmd-D's.

Andre

The DB is not broken, but for some reason the downloaded bodies seems corrupted or something.

What you can do is clear the cache for the subscriptions (see screenshot), then select all the messages in the subscription and do a CMD-D to re-download the bodies (if you want that)

Jaimie

Cool - I'll do that.

If there's anything I can supply to point the finger at bad server behaviour vs buggged Usenapp, let me know - otherwise I guess this is effectively fixed now. I've never seen it before and I've been using the server for literally a decade now.

Andre

To download a message body, Usenapp ask the news server for it by sending the message-id.
The data that the news server returns is directly written to a file on disk (cache) with the hash of the message-id as filename.

I don't see how Usenapp could fail in this process and produce a file with the content of two messages.
Moreover, nothing has changed to the code of this process since a long way back.

So either the news server failed or Big Sur failed or Usenapp went crazy (while upgrading).
I'll walk through the source code to see if anything could have caused this, but I hardly doubt I will find anything.

Also, remember that Big Sur is in an early beta phase and can cause weird things.

Jaimie

Nod nod. Not seen any data transmission glitches, but Big Sur does have an annoyingly twitchy wifi connection (although unless it happens during a web page refresh, I usually only notice when Usenapp shows the "Waiting for network" popup! Which is amazingly reactive by the way)

Jaimie

Found more today 🙁

Cmd-D (then clicking away and back) does fix them, but I'm a little concerned. As you say, it may be BS.

Jaimie

They're newly downloaded just now, rather than ones from the same incident.

Jaimie

Four of them seen scattered through rec.arts.sf.written, but the incorrect first half on each were all from the same thread in uk.comp.sys.mac.

Andre

I think I found a possible bug in Usenapp.
Please install this custom version and see how it goes?

-- link removed --

Jaimie

Got it in place now. Unfortunately it's another one of those "wait and see" reproduction bugs...
I'd not seen any today with 0.78.2.

Andre

Please upgrade to the latest 0.78.4 release that should have solved this issues.

Jaimie

Neat! Have done so. Didn't see any with 0.78.3 btw.

Andre

Jaimie Neat! Have done so. Didn't see any with 0.78.3 btw.

That was fixed in 0.78.3 indeed, but had created other problems.