Cairn

Timestamp carry-over ordering during in-place state compaction

NousResearch/hermes-agent · cluster 138355 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 3 PRs.

Three items concern _carry_parent_timestamps in in-place compaction: an issue reports it as a no-op because the archive runs before its donor query, so carried copies get now_ts and one message may render twice. Two PR titles propose fixes around preserving timestamps and moving the carry step before the archive.

Open issues1

  • Issue#138355`_carry_parent_timestamps` is a no-op in both in-place compaction paths: the archive runs before its donor query, so carried copies drift to `now_ts` and one logical message renders twice

Open PRs3

  • PR#138360fix(state): preserve timestamps during in-place compaction
  • PR#138364fix(state): carry parent timestamps before the archive, not after
  • PR#138377fix(state): run the timestamp carry before the in-place compaction archive
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/138355.json
cluster/138355.md