Project

General

Profile

Actions

Bug #3308

closed

ContentStore does not process ChildSelector and MustBeFresh

Added by Tai-Lin Chu about 9 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Tables
Target version:
-
Start date:
10/31/2015
Due date:
% Done:

0%

Estimated time:
Actions #1

Updated by Junxiao Shi about 9 years ago

  • Tracker changed from Task to Bug
  • Subject changed from NFD content store does not process ChildSelector and MustBeFresh to ContentStore does not process ChildSelector and MustBeFresh
  • Category set to Tables

Can @TaiLin provide steps to reproduce this bug? It can be either a code snippet, or command lines using ndnpeek or traffic generator.

If none is provided, I'll reject this bug after Nov 05 12:00 UTC.

Actions #2

Updated by Tai-Lin Chu about 9 years ago

It should be a task not a bug because it is not implemented yet. I am not sure what to provide here :)

Actions #3

Updated by Junxiao Shi about 9 years ago

  • Tracker changed from Bug to Task

Then, provide a detailed description on what should be implemented, and why is it needed.

Actions #4

Updated by Alex Afanasyev about 9 years ago

I am also very confused of what this issue is about and why it is task? NFD's Content Store processes both ChildSelector and MustBeFresh.

Actions #5

Updated by Tai-Lin Chu about 9 years ago

  • Status changed from New to Resolved

After some more debugging, it was a bug from our ansible script that accidentally checked out a very outdated version. I found out that when I sshed into one cluster node. False alarm, guys.

But I also notice a change in semantics that freshnessPeriod=0 was changed from "immediately stale" to "always fresh". Could you explain why?

Actions #6

Updated by Junxiao Shi about 9 years ago

  • Tracker changed from Task to Bug
  • Status changed from Resolved to Rejected
Actions

Also available in: Atom PDF