[Dxspider-support] Question about Spot::add_dup. build test-598

[Kin]

Dirk,

The following spot:

1742576798
PC61^28074.0^AF5CC^21-Mar-2025^1706Z^FT8^ES0IA^SK3W-6^91.129.104.85^H18^~

triggers all of this after the CHECKs:

1742576798^(spotdup) Spot::add_dup: ADD   (+INPUT+)   freq=28074.0
call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6
ipaddr='91.129.104.85'
1742576798^(spotdup) Spot::add_dup: ADD   (NORM TEXT) XAF5CC|ES0IA|28074|FT8
+600 secs STORE=>17:16:37Z
1742576798^(spotdup) Spot::add_dup: ADD   (QRG-CALL)  XAF5CC|28074
+305 secs STORE=>17:11:42Z
1742576798^(spotdup) Spot::add_dup: ADD   (CALL)      XAF5CC
+10 secs STORE=>17:06:47Z
1742576798^(spotdup) Spot::add_dup: ADD   (BY)        XES0IA
+10 secs STORE=>17:06:47Z
1742576798^(spotdup) Spot::add_dup: ADD   (IPADDR)    X91.129.104.85
+10 secs STORE=>17:06:47Z

The question is: how is it possible that the next two spots were labeled as
DUPE if the threshold wasn't exceeded? The three PC61s arrived in the same
second, right?

1742576798^(spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28074.0
call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6
ipaddr='91.129.104.85'
1742576798^(spotdup) Spot::add_dup: CHECK (NORM TEXT) XAF5CC|ES0IA|28074|FT8
DUPE=>17:16:37Z
1742576798^(spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28074.0
call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6
ipaddr='91.129.104.85'
1742576798^(spotdup) Spot::add_dup: CHECK (NORM TEXT) XAF5CC|ES0IA|28074|FT8
DUPE=>17:16:37Z

Kin EA3CV


-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 6190 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250321/c0f9abd2/attachment.bin>