Subj : rescan
To   : deon
From : Oli
Date : Sun Mar 14 2021 03:01 pm

deon wrote (2021-03-14):

 d>    Re: rescan
 d>    By: Oli to Avon on Sun Mar 14 2021 10:11 am

 Ol>> Your system successfully demonstrated the
 Ol>> 2-second/wrong-time-on-rescan bug of hpt (SMAPI) for real.

 d> I'm not following...?

 d> I'm wondering how a node doing a rescan can inject dupes into the
 d> network? Unless it was a "hub" that did the rescan from another node?

 d> (A quick check revealed my dups came via 2/1202 -> 2/100, but the origin
 d> of the messages came from varios hub 1 nodes.)

 d> But the 2 second bug in hpt wouldnt trap those? (I'm running an oldish
 d> build of hpt (probably due for an update as I have seen some development
 d> activity), and hub 3 tossed them all into the dupe message base (from
 d> what I can tell) - I'm assuming because of the msgid.)

I don't know. I received a couple of hundred dupes. I guess messages before Nov/Dec 2020 weren't in hub 3s dupe database.

My point is that this is a real world example that network-wide dupes caused by a rescan do happen. And that hpt does create unnecessary problems.

All dupes I see in the message base have an odd number of seconds in the original message's time.

q.e.d.

---
 * Origin: . (21:3/102)

.