Franz Busch

> > Would it be enough for you if we expose these by adding traces for the individual timings and metrics? > > No. These ought to be either observable...

Onboard with this idea. The current description is not really helpful in most cases and I always do a hexDump manually while debugging. We should also change the `debugDescription` of...

Yes `CustromStringConvertible` and `CustomDebugStringConvertible` are a bit messy. The latter is used by collection types to print their contents. So you should always implement both. At least that's my latest...

The reason I chose this name is that when you spell it out it reads `await gracefulShutdown()` which found better than `await waitForGracefulShutdown()`.

5.8 is out of the support policy already so this is expected https://forums.swift.org/t/dropping-support-for-swift-5-8-on-linux/78533

This might potentially look something like this: ``` try withSpan { span in throw CancellationError() } onError: { error, span in // Modify the span } ``` and/or we could...

You have two options here. Either you can create a logger and set the log level to `.warning` or higher. Then ServiceLifecycle won't do any logging or as @t089 said...