Jeremy Cline

I think there are two things that need to get fixed here: 1. Ack failures should be handled more gracefully in the read loop. 2. Something failed earlier on (which...

On 1/7/19 11:32 AM, Tomas Tomecek wrote: > I am trying to migrate our project from fedmsg to fedora-messaging. Thanks for filing a bug, you're the first person to try...

On 1/8/19 4:03 AM, Tomas Tomecek wrote: >> That is definitely the case. It was designed to work "out of the box" with a local message broker for quick and...

It's a known issue (https://pagure.io/fedora-infrastructure/issue/7493) with infra, seemingly related to the upgraded proxies. It is a convenient opportunity to see how many folks outside infra are consuming the messages, though!...

Hi @TomasTomecek, The Fedora message broker is now available outside of Fedora infrastructure and the RPM comes with a configuration file aimed at connecting to it. If it's not too...

Do you have any lingering questions, or can this issue be closed?

@abompard, I was thinking we could add a couple generally useful callbacks to a ``callbacks.py`` module (and move the printer out into that) that we document and maintain. That way...

> I think one of the easiest (though probably inefficient) ways to consume fedmsg was to just run `fedmsg.tail_messages()`. > > ```python > #!/usr/bin/python3 > import fedmsg > > #...

On 5/16/19 3:44 AM, Aurélien Bompard wrote: >> I guess it's worth writing a post-install script to run sed because that step is important. > > @jeremycline , I wonder...

> Since you said this step is important I wonder if fedora-messaging could detect if the 00000000-0000-0000-0000-000000000000 is in the queue name, assume it's a random consumer and generate a...