Cairn
NousResearch/hermes-agent

Telegram image cache stale content bug and fixes

Cluster 35242 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

A bug where the Telegram integration writes stale image content to new cache filenames, with related fixes addressing content-hash naming and retry logic for stale photo downloads from the Bot API.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: won't fix / by design 1 · other 1

  • #35260 fix(gateway): use content-hash filename in cache_image_from_bytes · won't fix / by design → #35242
  • #35263 fix(telegram): detect and retry stale photo downloads from Bot API (#35242) · other → #35242
Closed issues · 1
  • Closed#35242[Bug]: Telegram image_cache writes stale content from previous image to new filename
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/35242.json
cluster/35242.md