Own messages are synced messily if pre-empted by a remote message #37

Open
opened 2021-09-22 22:48:28 -04:00 by fair · 0 comments
Owner

If a Matrix message is sent, and an incoming LINE message is received & gets bridged before the outgoing Matrix message is successfully sent on LINE, the bridge gets confused and thinks the Matrix message may not have been bridged.

This can happen even if the outgoing Matrix actually did get bridged to LINE successfully, albeit possibly with a different interleaving of incoming/outgoing messages than is seen on the Matrix side. When that happens, the bridge sees the own-sent Matrix message as though it came from LINE, and bridges it. (So, at the very least, messages aren't lost when the bridge gets confused like this.)

A typical sequence of events is:

  1. Send Matrix message
  2. Receive LINE message right after
  3. Get a warning message of "Posting this message to LINE may have failed." as a reply to the message you sent
  4. Receive a duplicate of your message (as sent by you if using double-puppetting, or by the bridge bot otherwise)
If a Matrix message is sent, and an incoming LINE message is received & gets bridged before the outgoing Matrix message is successfully sent on LINE, the bridge gets confused and thinks the Matrix message may not have been bridged. This can happen even if the outgoing Matrix actually did get bridged to LINE successfully, albeit possibly with a different interleaving of incoming/outgoing messages than is seen on the Matrix side. When that happens, the bridge sees the own-sent Matrix message as though it came from LINE, and bridges it. (So, at the very least, messages aren't lost when the bridge gets confused like this.) A typical sequence of events is: 1) Send Matrix message 2) Receive LINE message right after 3) Get a warning message of "Posting this message to LINE may have failed." as a reply to the message you sent 4) Receive a duplicate of your message (as sent by you if using double-puppetting, or by the bridge bot otherwise)
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fair/matrix-puppeteer-line#37
No description provided.