I noticed that the logic to republish key-value pairs every hour seems to refresh the timestamp of the key-value pairs (via the _refresh_table method in network.py), thereby causing the TTL expiration deletion logic for the key-value pairs to become ineffective (if the expiration time is longer than the republishing interval). Is this intentional?
I noticed that the logic to republish key-value pairs every hour seems to refresh the timestamp of the key-value pairs (via the _refresh_table method in network.py), thereby causing the TTL expiration deletion logic for the key-value pairs to become ineffective (if the expiration time is longer than the republishing interval). Is this intentional?