mx-puppet-discord currently crashes #132

Closed
opened 2022-05-10 23:01:56 +00:00 by a · 6 comments
Owner

mx-puppet-discord upstream recently made a number of changes such as switching from npm to yarn, and the AUR package hasn't been updated yet to account for these changes. Node.js was also updated recently so I had to recompile (an older commit of) mx-puppet-discord with the current outdated PKGBUILD, but that build is crashing (although it did work exactly once, somehow). The Node.js update is why we can't use our existing build of mx-puppet-discord from a few months ago, because it's no longer compatible with Node 18.

mx-puppet-discord upstream recently made a number of changes such as switching from npm to yarn, and the AUR package hasn't been updated yet to account for these changes. Node.js was also updated recently so I had to recompile (an older commit of) mx-puppet-discord with the current outdated PKGBUILD, but that build is crashing (although it did work exactly once, somehow). The Node.js update is why we can't use our existing build of mx-puppet-discord from a few months ago, because it's no longer compatible with Node 18.
a added the
bug
label 2022-05-10 23:01:56 +00:00
a self-assigned this 2022-05-10 23:01:56 +00:00
Author
Owner

This is the error with the recompiled build:

× mx-puppet-discord.service - Matrix-Discord puppeting bridge
     Loaded: loaded (/usr/lib/systemd/system/mx-puppet-discord.service; enabled; vendor preset: disabled)
     Active: failed (Result: core-dump) since Tue 2022-05-10 18:05:30 CDT; 3s ago
    Process: 525312 ExecStart=node /usr/lib/node_modules/mx-puppet-discord/build/index.js -c /etc/mx-puppet-d>
   Main PID: 525312 (code=dumped, signal=SYS)
        CPU: 39ms

May 10 18:05:30 exozyme systemd[1]: Started Matrix-Discord puppeting bridge.
May 10 18:05:30 exozyme systemd[1]: mx-puppet-discord.service: Main process exited, code=dumped, status=31/SYS
May 10 18:05:30 exozyme systemd[1]: mx-puppet-discord.service: Failed with result 'core-dump'.
This is the error with the recompiled build: ``` × mx-puppet-discord.service - Matrix-Discord puppeting bridge Loaded: loaded (/usr/lib/systemd/system/mx-puppet-discord.service; enabled; vendor preset: disabled) Active: failed (Result: core-dump) since Tue 2022-05-10 18:05:30 CDT; 3s ago Process: 525312 ExecStart=node /usr/lib/node_modules/mx-puppet-discord/build/index.js -c /etc/mx-puppet-d> Main PID: 525312 (code=dumped, signal=SYS) CPU: 39ms May 10 18:05:30 exozyme systemd[1]: Started Matrix-Discord puppeting bridge. May 10 18:05:30 exozyme systemd[1]: mx-puppet-discord.service: Main process exited, code=dumped, status=31/SYS May 10 18:05:30 exozyme systemd[1]: mx-puppet-discord.service: Failed with result 'core-dump'. ```
a started working 2022-05-11 19:03:24 +00:00
Author
Owner

The coredump is because of excessive systemd hardening.

The coredump is because of excessive systemd hardening.
Author
Owner

OK, I'm dumb.

Yesterday when debugging this, I uninstalled mx-puppet-discord with pacman -Rns, where the -n removes config files. So when testing today, the config file was just the default, which caused all sorts of issues!

OK, I'm dumb. Yesterday when debugging this, I uninstalled mx-puppet-discord with `pacman -Rns`, where the `-n` removes config files. So when testing today, the config file was just the default, which caused all sorts of issues!
a closed this issue 2022-05-11 19:16:07 +00:00
a stopped working 2022-05-11 19:16:07 +00:00
12 minutes 43 seconds
a added this to the (deleted) project 2022-05-11 19:36:05 +00:00
a reopened this issue 2022-05-14 00:09:53 +00:00
a started working 2022-05-14 00:09:55 +00:00
Author
Owner

It's crashing again...

I should report this to the AUR maintainer.

It's crashing again... I should report this to the AUR maintainer.
Author
Owner

OK, this is bizarre: Discord -> Matrix messages work, but not the other way around.

OK, this is bizarre: Discord -> Matrix messages work, but not the other way around.
Author
Owner

Yay, a manual Git clone and build works! 🎉 I'll report this to the AUR maintainer.

Yay, a manual Git clone and build works! 🎉 I'll report this to the AUR maintainer.
a closed this issue 2022-05-14 00:28:24 +00:00
a stopped working 2022-05-14 00:28:24 +00:00
18 minutes 29 seconds
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 31 minutes 12 seconds
a
31 minutes 12 seconds
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: exozyme/exozyme#132
No description provided.