Return full stacktrace on service startup failures

Is your feature request related to a problem? Please describe.

I’d like to see if service stacktraces can be bubbled up during service startup.

While writing integration tests for a service the gRPC call would fail with an unknown error and the detailed error messages and adding log interceptors didn’t make it any clearer to me where the issue was. The root cause was IConfiguration wasn’t being passed into my service on startup during the test so some values were null and causing the service to not start up, but if the stackstrace was easily available, without having to debug the pkg, it would have reduce the amount of code to look though for the cause.

Describe the solution you’d like

Specifically this call was discarding the stacktrace during startup due to the finally, could we catch the exception and bubble it up here?

        private async Task<TResponse> ResolvedInterceptorInvoker(TRequest resolvedRequest, ServerCallContext resolvedContext)
        {
            GrpcActivatorHandle<TService> serviceHandle = default;
            try
            {
                serviceHandle = ServiceActivator.Create(resolvedContext.GetHttpContext().RequestServices);
                return await _invoker(serviceHandle.Instance, resolvedRequest, resolvedContext);
            }
            finally
            {
                if (serviceHandle.Instance != null)
                {
                    await ServiceActivator.ReleaseAsync(serviceHandle);
                }
            }
        }

Describe alternatives you’ve considered

Log interceptors weren’t that helpful since it doesn’t tell you which code the error came from.

Additional context

It would also be nice if IConfiguration was injected during the test, but that’s likely a different ticket.

[JamesNK]

I improved the example here - https://github.com/grpc/grpc-dotnet/pull/1841

[cove]

Oh I see, I just copied the sample code verbatim and didn’t look too closely at it, so that’s where it’s getting dropped then:

       private void WriteMessage(LogLevel logLevel, string category, EventId eventId, string message, Exception? exception)
        {
            // Log using the passed in execution context.
            // In the case of NUnit, console output is only captured by the test
            // if it is written in the test's execution context.
            ExecutionContext.Run(_executionContext, s =>
            {
                Console.WriteLine($"{_stopwatch.Elapsed.TotalSeconds:N3}s {category} - {logLevel}: {message}");
            }, null);
        }

Also any thoughts on why the IConfiguration isn’t loading values from appsettings.json in the test?