[Dxspider-support] Is dedupe really working?

[Kin]

Hi Andrea,
 
Using build 562
 
With a configuration like yours:
 
set/var $Spot::timegranularity = 60
set/var $Spot::dupage = 1800
 
I execute: clear/dupe
 
I have sent (attempted) the following spots:
 
dx 0TEST 7070 test ignore    <-- 1928Z
dx 0TEST 7070 test ignore    <-- 1928Z
dx 0TEST 7070 test ignore    <-- 1930Z
dx 0TEST 7070 test ignore    <-- 1930Z
dx 0TEST 7070 test ignore    <-- 1931Z
 
The ones I attempted to send within the same minute inform me of:
 
dx 0TEST 7070 test ignore
Sorry, this is a duplicate
 
Which is correct.
 
If I look at the traces for dxdupe:
 
1738438088537^(dxdupe) DXDupe::add key: X0TEST|EA3CV|7070|1738438080|TEST IGNORE time: 1958Z
1738438244761^(dxdupe) DXDupe::add key: X0TEST|EA3CV|7070|1738438200|TEST IGNORE time: 2000Z
1738438296731^(dxdupe) DXDupe::add key: X0TEST|EA3CV|7070|1738438260|TEST IGNORE time: 2001Z
 
As expected, there are only 3 entries corresponding to the spots that were sent to the network.
After 30 min, it can be verified that in dupefile there are only spots with < 30 min.
My conclusion is that the timegranularity of 1 min and the 30 min dupage have been respected.
 
sh/dx 0TEST
   7070.0 0TEST        1-Feb-2025 1931Z test ignore         <EA3CV>
   7070.0 0TEST        1-Feb-2025 1930Z test ignore         <EA3CV>
   7070.0 0TEST        1-Feb-2025 1928Z test ignore         <EA3CV>
 
I believe it is working.
 
Kin EA3CV
 
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de IZ2LSC via Dxspider-support
Enviado el: sábado, 1 de febrero de 2025 15:49
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: IZ2LSC <iz2lsc.andrea at gmail.com>
Asunto: Re: [Dxspider-support] Is dedupe really working?
 
It seems that nobody is interested in de-dupe not working.
I'm a little bit surprised because this could potentially highly increase the number of spots circulating in the network.
>From my side I will not update my node until this issue is resolved.
 
>From my test node I can see that the dupes files is populated but not enforced.
 
view_dupes
IZ2ABC|IZ2TEST|7070|1738420620||TEST1 =  1-Feb-2025 1437Z expires  1-Feb-2025 1507Z
IZ2ABC|IZ2TEST|7070|1738420680||TEST1 =  1-Feb-2025 1438Z expires  1-Feb-2025 1508Z
IZ2ABC|IZ2TEST|7070|1738420740||TEST1 =  1-Feb-2025 1439Z expires  1-Feb-2025 1509Z
IZ2ABC|IZ2TEST|7070|1738420800||TEST1 =  1-Feb-2025 1440Z expires  1-Feb-2025 1510Z
 
73
iz2lsc
 
-->
 
 
On Sat, Feb 1, 2025 at 8:02 AM IZ2LSC <iz2lsc.andrea at gmail.com <mailto:iz2lsc.andrea at gmail.com> > wrote:
Any idea?
Am I wrong?
TNX
Andrea
/// sent from my mobile device \\\
 
Il ven 31 gen 2025, 19:15 IZ2LSC <iz2lsc.andrea at gmail.com <mailto:iz2lsc.andrea at gmail.com> > ha scritto:
Doesn't seem so.
Running latest build in a lab environment on NODE B
DXSpider v1.57 (build 562 git: mojo/691ed8f6[r]) using perl v5.34.0 on Linux
Spot are generated locally on NODE A and forwarded to NODE B
spot------>NODE A --------> NODE B 
 
Output from NODE B
sh/dx
   7090.0 IZ2ABC      31-Jan-2025 1804Z test2                       <IZ2TEST>
   7090.0 IZ2ABC      31-Jan-2025 1803Z test2                       <IZ2TEST>
   7090.0 IZ2ABC      31-Jan-2025 1802Z test2                       <IZ2TEST>
   7090.0 IZ2ABC      31-Jan-2025 1801Z test2                       <IZ2TEST>
 
sh/var $Spot::qrggranularity
$Spot::qrggranularity = 5

sh/var $Spot::timegranularity
$Spot::timegranularity = 60

sh/var $Spot::dupage
$Spot::dupage = 1800
 
 
Andrea, iz2lsc
 
-->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250201/d64d0182/attachment-0001.htm>