Cairn
NousResearch/hermes-agent

Telegram replies with non-numeric reply anchor ids

Cluster 139611 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

Members concern Telegram reply anchors that are not numeric message ids, where one report describes raw int() parsing of wake-identity JSON crashing replies since v0.22.1. Two pull requests propose sending the message unanchored instead of crashing; this describes proposals, not confirmed outcomes.

Open issues1

  • Issue#139611[Bug]: Telegram reply anchors crash on non-numeric ids since v0.22.1 — raw int() on wake-identity JSON kills every reply into affected sessions

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #139642 fix(telegram): send unanchored when a reply anchor is not a message id (#139611) · other → #140185
  • #139644 fix(telegram): send unanchored instead of crashing on non-numeric reply anchors · superseded by another PR → #139642
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.67: 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
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/139611.json
cluster/139611.md