On Mon, 2022-07-11 at 09:35 +0200, Pierre-Yves Chibon wrote:
> On Sat, Jul 09, 2022 at 09:36:14AM -0400, Stephen Smoogen wrote:
> > On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius <rc040203@freenet.de>
> > wrote:
> >
> > > Hi,
> > >
> > > I thought the notification delay mess was fixed. Apparently, I
> > > was wrong.
> > >
> > >
> >
> > No, I believe the service which is behind these emails is called
> > FMN. It is
> > very fragile for multiple reasons where it falls over for different
> > reasons
> > all the time. It is the reason why it is on the top of being
> > replaced by
> > CPE in this quarter (aka by October-ish).
>
> Just a quick note, I doubt the app will be re-written and deploy in a
> single
> quarter, I expect this to be more a multi-months effort. So while it
> has the top
> of the priority list for CPE to work on, it'll still take a little
> time before
> we see a v4 (we've already restructured it 3 times).
>
I think you should disable the service or allocate someone to do
something that mitigate the problem or reboot the service every time it
stops
Like many services in Fedora, it is intertwined with other tools with a bunch of duct tape and bailing wire that was going to be fixed when things slowed down. You can't just disable it because then you cause other items inside and outside of Fedora to break. You can't just reboot it because the problem is usually some other service which is causing the holdup.
There are days when I regret leaving Fedora Infrastructure, but it is email threads like this which remind me why I needed to.