Cairn

File attachment delivery failures silently reported as success

NousResearch/hermes-agent · cluster 13356 · gateway

Data as of

7 open items. Fix attempted, not merged.

The short answer

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

Multiple issues and fixes address Telegram and Mattermost incorrectly reporting successful sends when file attachments were missing, invalid, or never delivered. Work spans detection, error surfacing, and channel post media handling.

Open issues3

  • Issue#51543# Bug Report: Telegram channel file attachments not delivered
  • Issue#52126fix: Telegram channel file attachments silently dropped in _handle_media_message
  • Issue#65858Mattermost says a missing attachment was sent successfully

Open PRs4

  • PR#13933fix(gateway): fail Telegram document sends on invalid files
  • PR#34178fix(gateway): surface dropped MEDIA paths in send_message result
  • PR#51747fix(telegram): cache channel-post media via effective_message (#51543)
  • PR#65863fix(mattermost): report missing attachments as failed

3 PRs closed without merging

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

  • #13440 fix(telegram): ensure file attachments are actually delivered (fixes #13356) · other → #13356, #13421, #13434
  • #52131 fix(telegram): use effective_message in _handle_media_message for channel posts (#52126) · superseded by another PR → #51747
  • #75001 fix(mattermost): report a missing local file as a failed send (#65858) · superseded by another PR → #65863, #65858
Closed issues · 2
  • Closed#13356Telegram text delivery works, file attachments report success but never arrive
  • Closed#32644Telegram MEDIA audio attachment can report success while delivering no attachment
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.13: 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
2
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/13356.json
cluster/13356.md