Matrix connector reply_to parameter name bug
NousResearch/hermes-agent · cluster 1842 · gateway
Data as of
Nothing open on GitHub. Fix merged in #1895. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #1895. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #1895. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests concern an incorrect parameter name used when constructing a Matrix MessageEvent, specifically around the reply_to vs reply_to_message_id field. Multiple fixes and a bug report address the same naming discrepancy in the Matrix connector.
Open issues0
Open PRs0
Fixes on record
-
#1895 fix(matrix): use correct reply_to_message_id parameter name
files:
gateway/platforms/matrix.py
3 PRs closed without merging
From the close comments: done elsewhere 2 · merged via another change 1
- #1846 fix(matrix): correct reply_to parameter name to reply_to_message_id in MessageEvent · done elsewhere
-
#1848 fix: correct reply_to param name in Matrix MessageEvent construction · done elsewhere →
#1895 -
#1885 fix(matrix): use correct reply_to_message_id parameter name · merged via another change →
#1895
Closed issues · 1
- Closed#1842[Bug]: Incorrect parameter name in Matrix connector MessageEvent construction
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #1895
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 18 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.