Upgrading to the latest version of Serilog causes infinite loop about serilog-sinks-slack

[TrapperHell]

That's pretty hard to diagnose especially without any backing code that is producing this problem.

In common usage the latest version of the code doesn't / shouldn't produce stack-overflow exceptions within the Dispose method.

Are you using a ConcurrentDictionary to keep track of the dependencies? Are you trying to reload the logging configuration / logger?

Are you sure that the issue occurs only with the latest version? Would reverting to a prior version resolve the issue?

[jgwconsulting]

Thanks for getting back to me, and sorry for dumping a half-baked issue on you :) I'll do some proper digging and local debugging and let you know how I get on. It's a hugely useful extension for us, so we're really missing it.

[rikdepeuter]

We're running into the same problem. We started experiencing it after upgrading from dotnet6 to dotnet8 and updating SlackSink to 2.2.2. Downgrading SlackSink back to the original version 2.2.1 doesn't have any impact.
We only get the error spam when the host stopped.

Edit: when I downgrade back to dotnet6, there's no more StackoverflowException with the same SlackSink version.