UnobservedTaskException after Client.Disconnect() about smblibrary

[TalAloni]

Thanks Nick,
Did this issue occur on 1.5.1.2?

[nixtar]

Sorry for the delay,

Yes, this is on 1.5.1.2. I just tested now on 1.5.1.1 and the exception is not thrown.
This makes sense however as Close is not being called.

For now as a workaround, I've added a check for this particular exception in our UnobservedTaskException handler and am ignoring it.

[TalAloni]

Thanks Nick,
I've spent some time on this,
Using the example you provided, I can see the exception being thrown in a thread pool thread in .NET 6.0.
Interestingly, this does not happen when running under .NET Framework 2.0 and .NET Framework 4.0.
After trying various code changes, it's not clear to me what I can do (within reason) to avoid that behavior.
It's noteworthy that even without calling Socket.Close I'm observing that behavior. (Disconnect triggers it as well)

Given that this is a logging issue rather than an operational bug, and given that I believe I'm following the documentation, I'm closing this issue.
If you have a suggestion on how to address this issue, I'll gladly look into it.

[nixtar]

Yeah that's fair enough, I also can't see a way forward without possibly refactoring all the socket handling and likely breaking compatibility with older dotnets. (eg not using Begin* methods)

Thanks for your efforts regardless. 👍