bug#71144: Interactive prompt opened upon shepherd config file error

2024-05-25 Thread Ludovic Courtès
Christopher Baines skribis: > That looks good to me, the "Arrange to spawn a REPL if something goes > wrong" comment needs removing/updating, but that's the only thing I > spotted. Cool. I updated the comment and pushed it as cca25a67693bb68a1884a081b415a43fad1e8641. Thanks! Ludo’.

bug#71144: Interactive prompt opened upon shepherd config file error

2024-05-25 Thread Christopher Baines
Ludovic Courtès writes: > Ludovic Courtès skribis: > >> I think we should change the above to log and gracefully handle failure >> to load an individual service file. > > With the change below, every service except the offending one is loaded > and started as expected: > >

bug#71144: Interactive prompt opened upon shepherd config file error

2024-05-25 Thread Ludovic Courtès
Ludovic Courtès skribis: > I think we should change the above to log and gracefully handle failure > to load an individual service file. With the change below, every service except the offending one is loaded and started as expected: --8<---cut

bug#71144: Interactive prompt opened upon shepherd config file error

2024-05-23 Thread Ludovic Courtès
Hello, One problem we noticed in the analysis of the boot problem of bayfront after the recent downtime¹ is that an interactive REPL would be opened after an unbound variable was found in the shepherd config file: --8<---cut here---start->8--- [ 13.098907]