wee-slack: WS ERROR with latest weechat
Thank you for this awesome plugin! 🙏
I’m seeing a very strange issue with wee-slack when using the latest weechat. I’m getting a Python WS ERROR as soon as I try to send a message somewhere. I’m using ArchLinux and see this issue as soon as I use either weechat@2.3-2 or weechat-git.
As soon as I downgrade to weechat@2.3-1 it works as expected. What is even more strange is that the difference, from what I can see, between weechat@2.3-1 and weechat@2.3-2 is Ruby rebuild for 2.6.
I can easily replicate this and I’ve tried it so far on three machines. Let me know how I can further help to solve this issue! 🍻
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 4
- Comments: 28 (14 by maintainers)
I see that Arch has actually applied my patch to the package. So if you’re using Arch, and websocket-client installed with pacman, you can just update.
I think so and I am on Arch Linux too
@trygveaa
Currently running the latest commit on
master(82c00c5a574b5cb9f78852acb9b8ba77ea89458f).The slack buffer is continuously outputting:
The slack-debug buffer is continuously outputting:
When trying to send a message the weechat buffer outputs:
Give me a ping if I can provide anything else.