NFD

The current implementation (omitted FreshnessPeriod means infinity) appears to have an effective FreshnessPeriod of 99999ms.
In nfd::cs::Entry::updateStaleTime() function, I added:

std::cout << this->getName() << ' ' << time::steady_clock::now() << ' ' << m_staleTime << '\n';

And I got:

/A/5 0 nanoseconds since unit test clock advancements 99999000000 nanoseconds since unit test clock advancements
/A/5 203850304910641 nanoseconds since boot 203950303908994 nanoseconds since boot

However, setting FreshnessPeriod to an explicit value greater than 99999ms works correctly.

Junxiao Shi wrote:

The current implementation (omitted FreshnessPeriod means infinity) appears to have an effective FreshnessPeriod of 99999ms.
In nfd::cs::Entry::updateStaleTime() function, I added:

std::cout << this->getName() << ' ' << time::steady_clock::now() << ' ' << m_staleTime << '\n';

And I got:

/A/5 0 nanoseconds since unit test clock advancements 99999000000 nanoseconds since unit test clock advancements
/A/5 203850304910641 nanoseconds since boot 203950303908994 nanoseconds since boot

However, setting FreshnessPeriod to an explicit value greater than 99999ms works correctly.

It looks like the CS unit test fixture was setting the FreshnessPeriod of stored data to 99999ms by default. I removed this.

https://gerrit.named-data.net/#/c/3883 to ndn-cxx causes unit test failures in ndn-tools and possibly other projects.

The issues in ndn-tools mentioned in note 7 should be fixed in the new patchset posted for ndn-cxx and with the new change pushed for ndn-tools (https://gerrit.named-data.net/#/c/3899/).