ntfy adapter UTF-8 byte limit enforcement

NousResearch/hermes-agent · cluster 105287 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 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 2 PRs.

These items address a bug where the ntfy adapter truncated messages by character count rather than byte count, which is incorrect given ntfy's byte-based message size limit. The work focuses on ensuring non-ASCII content is also kept within the byte limit.

Open issues1

  • Issue#105287ntfy adapter truncates by characters, but ntfy's message limit is bytes

Open PRs2

  • PR#105309fix(ntfy): keep non-ASCII replies within the message limit
  • PR#105313fix(ntfy): enforce the message body limit in UTF-8 bytes (#105287)
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
0 PRs closed without merging

For your agent

The same facts, typed.