I don't understand why this is non-trivial. service_manager::RunStandaloneService is only invoked by service_manager::Main, so we can just remove the Init call from RunStandaloneService.

There are probably also other cases in certain unit test suites where we suffer from duplicate initialization, but those are less concerning I think.

Sorry, I meant making sure Init is called once in "all possible initialization" paths (including in tests) is not trivial :)


Yes, one can fix just the RunStandaloneService case as you suggested (however, also note that in that scenario the 2nd call actually changes the config and that should be handled, too).

Right, we want the configuration from service_manager::Main anyway though.