mirror of
https://github.com/open-webui/computer.git
synced 2026-11-05 01:17:24 +00:00
[GH-ISSUE #148] bug: Signal rest api communication not working #74
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/computer#74
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Georg311 on GitHub (Jul 16, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/148
I don't know if it is just an issue on my setup or if it's an issue in cptr. With the following change the bridge works for me, but i'd be happy if somebody would cross check for me.
I've instantiated a docke rest bridge with following command
Then i've tried to connect the signal bridge to it, but it fails everytime with the following error
Error Message in cptr log
The Signal Rest bridge works itself if used manually via curl commands
My proposed fix for this would be something like this:
which should acommodate for both cases (dict and list) (or we could just delete /restructure the logger info)
also because right now the signal adapter / bridge doesn't support streaming properly it leads to signal not properly managing messages
So if i send a signal message i get the initial "Thinking ..." Prompt, but afterwards nothing happens on the signal side.
The request is still sent to the llm, the answer is sent back to cptr but the message never makes it back to signal
I've also changed the edit command to just send the message instead as new message, which means you first get the "Thinking ..." and afterwards the answer, but i think that's a tradeoff that should work.
With those 2 changes the signal bridge works (i can send and receive messages (even if it is of course spammy in comparison to e.g. telegram)
I've summarized all my changes in this commit, if you want to take a look
github.com/open-webui/computer@83a6eeb121@owui-terminator[bot] commented on GitHub (Jul 16, 2026):
⚠️ Missing Issue Title Prefix
@Georg311, your issue title is missing a categorising prefix (e.g.
bug:,feat:,docs:).Please update the title to lead with one of:
Example:
bug: Login fails when the password contains special characters@owui-terminator[bot] commented on GitHub (Jul 16, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
This is the only directly adjacent issue I found around Signal/bridge behavior, but it is actually about repeated response output and missing stream termination rather than Signal REST API compatibility or the connect-time AttributeError. It may still be tangentially relevant to the user’s note about streaming not working properly.
by JKGeovision
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
@Georg311 commented on GitHub (Jul 16, 2026):
As far as i can tell this issue has nothing to do with the one referenced
@tjbck commented on GitHub (Jul 16, 2026):
Should be addressed, Testing wanted here!
@Georg311 commented on GitHub (Jul 18, 2026):
Just wanted to tell you, signal 1:1 messages work now! Signal to group messages don't work (messages are always sent to the 1:1 chat of the person sending the message instead of the group)