bug: appservices receive duplicated events

nex commented

2025-04-14 20:29:10 +00:00

Owner

more info required

nex added the

Bug

label

2025-04-14 20:29:10 +00:00

Jade commented

2025-04-14 20:31:19 +00:00

Owner

Logs from mautrix-discord's side:

Logs from mautrix-discord's side: ![image](/attachments/7e89460b-d037-42f0-be01-5e72da5cbf72)

image.png

215 KiB

Jade commented

2025-04-14 20:32:14 +00:00

Owner

Some people with similar setups haven't encountered this, so may be to do with database corruption caused by the appservice EDU patch

Jade added the

Matrix/Appservices

label

2025-04-14 21:01:08 +00:00

nex commented

2025-04-14 21:22:00 +00:00

Author

Owner

@Jade wrote in continuwuation/continuwuation#739 (comment):

Some people with similar setups haven't encountered this, so may be to do with database corruption caused by the appservice EDU patch

I've managed to repro on transgender.ing before, which never ran the patch. Can't say for sure

@Jade wrote in https://forgejo.ellis.link/continuwuation/continuwuation/issues/739#issuecomment-14634: > Some people with similar setups haven't encountered this, so may be to do with database corruption caused by the appservice EDU patch I've managed to repro on transgender.ing before, which never ran the patch. Can't say for sure

nex added a new dependency

2025-04-14 21:22:35 +00:00

#751 feat: appservice callbacks

nex referenced this issue

2025-04-14 21:23:03 +00:00

feat: appservice callbacks #751

nex added the

labels

2025-05-31 00:07:02 +00:00

Henry-Hiles commented

2025-09-28 16:27:35 +00:00

Contributor

Can reproduce with OOYE, never ran whatever patch that was. Can I ask if the repeat messages would have different txnids?

NoaHimesaka1873 commented

2026-01-24 18:47:12 +00:00

Can reproduce, also it seems to happen when lots of events are firing at the same time, like redacting message or banning user on multiple rooms.

NoaHimesaka1873 commented

2026-01-25 12:36:37 +00:00

@NoaHimesaka1873 wrote in #739 (comment):

Can reproduce, also it seems to happen when lots of events are firing at the same time, like redacting message or banning user on multiple rooms.

More specifically, for me, it happens when Meowlnir sending "Redacted (n) events from (user) in (channel)" message, and this message getting bridged by mautrix-discord bot.

@NoaHimesaka1873 wrote in https://forgejo.ellis.link/continuwuation/continuwuity/issues/739#issuecomment-23270: > Can reproduce, also it seems to happen when lots of events are firing at the same time, like redacting message or banning user on multiple rooms. More specifically, for me, it happens when Meowlnir sending "Redacted (n) events from (user) in (channel)" message, and this message getting bridged by mautrix-discord bot.

autumn commented

2026-02-26 23:33:02 +00:00

Contributor

How can I help debug this? I am pretty sure I am hitting this problem with OOYE and duplicated messages.

Happy to dig into code/compile stuff etc.

How can I help debug this? I am pretty sure I am hitting this problem with OOYE and duplicated messages. Happy to dig into code/compile stuff etc.

Jade commented

2026-02-26 23:34:36 +00:00

Owner

First step is likely getting a debug build with traces going, and then watching for suspicious logs around appservices. It might be easier if you can reproduce it in an artificial environment

autumn commented

2026-02-27 00:12:47 +00:00

Contributor

Lemme put up a debug homeserver setup.

autumn commented

2026-02-27 00:54:11 +00:00

Contributor

Set up a brand new homeserver and ooye instance with dev continuwuity + trace

Set up a brand new homeserver and ooye instance with dev continuwuity + trace![image](/attachments/32a54dce-942a-4cc4-916d-efc525671d95)

image.png

37 KiB

autumn commented

2026-02-27 00:55:22 +00:00

Contributor

Blah:

warning: some trace filter directives would enable traces that are disabled statically
 | `trace` would enable the TRACE level for all targets
 = note: the static max level is `info`
 = help: to enable DEBUG logging, remove the `max_level_info` feature from the `tracing` crate

wtfrog sec...

Blah: ``` warning: some trace filter directives would enable traces that are disabled statically | `trace` would enable the TRACE level for all targets = note: the static max level is `info` = help: to enable DEBUG logging, remove the `max_level_info` feature from the `tracing` crate ``` wtfrog sec...

Jade commented

2026-02-27 00:57:02 +00:00

Owner

You have to build with --no-default-features --features default to get all log levels I believe.

autumn commented

2026-02-27 00:57:44 +00:00

Contributor

Hmm... The way you are meant to build the container is just the Dockerfile in /docker right?

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/sbin/conduwuit": stat /sbin/conduwuit: no such file or directory

Hmm... The way you are meant to build the container is just the Dockerfile in `/docker` right? ``` Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/sbin/conduwuit": stat /sbin/conduwuit: no such file or directory ```

autumn commented

2026-02-27 00:59:06 +00:00

Contributor

Also something to note... that Out of Your Element bot was repeating its own messages there...

autumn commented

2026-02-27 17:40:48 +00:00

Contributor

Think I figured out my problem, I was not using buildx, just trying to manually build and it missed a bunch of stages.

Rows
Columns

bug: appservices receive duplicated events #739