Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

post an error in room if a user sends a message in a bridged room, but the bridge doesn't/can't send the message #25

Open
ericmigi opened this issue Jan 30, 2020 · 2 comments

Comments

@ericmigi
Copy link
Contributor

I sent a message via riot to a bridged slack room at 23:53, but the bridge didn't forward to slack and didn't error out.

Here are the logs from mx-puppet-slack

Jan-29 23:53:28.888 [bot-sdk-Appservice] info: Processing transaction 3911
Jan-29 23:53:28.890 [bot-sdk-Appservice] info: Processing event of type m.room.message
Jan-29 23:53:28.904 [PuppetBridge] info: New message by @eric:eric.nova.chat of type m.room.message to process!
172.20.0.2 - - [29/Jan/2020:23:53:28 +0000] "PUT /transactions/3911?access_token= HTTP/1.1" 200 2 "-" "Synapse/1.7.2"
Jan-30 00:53:29.000 [RoomSync] info: Maybe leaving ghost @eric:eric.nova.chat from !YQSUYdeTAk:eric.nova.chat

but no message was sent to slack.

@Sorunome
Copy link
Owner

Sorunome commented Feb 2, 2020

Unfortunately, due to the nature of things, each protocol implementation will have to do that on their own. mx-puppet-discord does this already, though

@ericmigi
Copy link
Contributor Author

ericmigi commented Feb 3, 2020

Ok, I'll close this and open in each protocol if that's better (just to track)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants