-
Notifications
You must be signed in to change notification settings - Fork 615
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
Bot silently fails and not does bridge messages between IRC and Slack #642
Comments
Firstly, the good news: this is a great bug report. Thankee, sai! The alao good news: it's fixed! #639 (comment) The bad news: I am not so good at using snowclone phrasal constructs Deep apologies for the bother with the breakage. |
@patcon Oh, super! Following the advice in #639 (comment), I downgraded to v1.12.0 for now and the bridge works as expected. It would be great to get a new release cut with this fix if possible. 🙂 |
Might be a little while -- we don't tend to release quite that often. @42wim's call. But to clarify, master is always built here: Despite the link in the other thread perhaps appearing to be 1.12.0, it's in fact the most recent mainline automated build (untagged) If releases are important to you, I suspect we'd be grateful for help investigating ways to make very frequent releases less of a burden. If you were eager, of course! Again, this is up to @42wim to decide, but maybe things like scripts or researching a semantic release process for Go? If you would be willing to offer your time, please do open up a new issue! 🎉 |
Also, would you mind closing this out? :) |
@jwflory 1.12.2 is out with the fix :-) |
I deployed this in FOSSRIT/infrastructure@54201fc and everything is looking good so far. Thanks for the quick resolution to this ticket. 😄 |
Ah sweet! Thanks! Would it be worthwhile to cut that out into a unit (playbook?)? I cut my teeth in chef, so not sure if ansible necessarily works best this way :) But either way, we should at the very least link your role in the related projects section: If you're game, we'd be psyched to merge a PR for that! 🐱🐱🐱 |
(And I'd wait for @42wim on the release script ask, before you spend valuable attention on it :) ) |
We're using an Ansible Role to do this now. From the docs, they are explained like this:
This way, anyone should be able to take the role and use it in their own playbook. You can see how this is used in a playbook here.
Cool! Done in #643. 🙂 |
Hey, I think the releases are already agile and semver, that's my goal anyway :) |
That is rad wim. Sorry, I didn't realize :) Semantic release is a little diff from semver fwiw. But if that's not something we'd appreciate from a devops-minded contributor, it might be interesting more generally to riff on ops tasks (in chat channel?) that ppl with those skills could work on. eg, documenting use with pleaserun or things like that. (Pleaserun has great "project principles" section in the readme btw) |
Ok misread the sem release and semver. So it's basically the same as the dev builds I'm already doing. Not a fan of making official releases that way. People have enough options already. stable builds, devbuilds, diy builds. Regarding to pleaserun, we have a journald service file in contrib. Instead of building, generating, maintening those files I think it would be better to get matterbridge into the different distros. But let's discuss this further on the chat. |
From my point of view, it was a seamless process and one of the quickest turnarounds I've ever had on an upstream bug being fixed, so no complaints here. 🙌
I have a lot of experience in the Fedora community. I'm happy to offer support and guidance for what that process looks like and what to do in the Fedora community. |
Oh hey, rockin! Would you be so generous to pop open a general ticket about it, @jwflory? @42wim prob has some thoughts on what he's hoping for, but any references you know would be welcome. (You don't necessarily have to be the one to do the work, but it would be totally welcome if you had time! :) |
Description
Bot successfully starts and claims to join IRC channels, but:
To reproduce
Steps to reproduce the behavior:
Run the bot with this config and these variables:
Expected behavior
/usr/local/bin/matterbridge -conf matterbridge.toml
)Debug logs
More information is also in FOSSRIT/infrastructure#21.
Nothing happens after this message. Even when other activity on either side of the bridge happens, there is silence.
Environment
The text was updated successfully, but these errors were encountered: