Symptom
A hosted group room never runs member turns. Calling HostedRoomServerRPC.submit the way the driver does raises TypeError: HostedRoomServerRPC.submit() missing 1 required keyword-only argument: 'member_id'. The task stays running and no log line names the error.
Evidence what you'll see
- The issue reproduces the driver's call at
tui_gateway/hosted_room_driver.pylines 593-597 and getsTypeError: HostedRoomServerRPC.submit() missing 1 required keyword-only argument: 'member_id'. - The member never replies. The room task stays
running. The driver cannot tell that boundary failure from an ambiguous post-submit observation failure. prompt.submitrequires a non-emptymember_idin the hosted-task proof, somember_id=""is not a fix.
Why it happens
The unified gateway runtime merge dropped member_id from the driver's transport.submit(...) call and from the InternalSessionRPC protocol, while HostedRoomServerRPC.submit still requires it as a keyword-only argument. Pull request 138753 restores member_id=_member_id(task) on that submit and declares the argument on the protocol.
Affected versions
Hermes at eb75627faf532fa6ffbdae59a0d14b0b385fc780 and 297552a9d646; last working 6ebd92d93852. Ubuntu 24.04, Linux x86_64, Python 3.14.7. Native Hermes hosted group rooms.
Fix steps
0 of 2 done
Your check marks stay in this browser only.
How to check it worked
- A hosted group room with a local member bot replies to a message that should get a member turn. The submit does not raise
missing 1 required keyword-only argument: 'member_id'.
If it still fails
- No published release tag contains pull request 138753. Tag
v0.22.2was compared against mergedfa793897732and does not contain it. - The same call can still forward an
attachmentskeyword that the in-process transport does not accept; that is a separate defect tracked as issue #138684 and pull request #138743.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it