Closed theolivenbaum closed 9 months ago
Probably introduced by this change.
We have seen the same with this release.
Thanks for raising this, I have unlisted v9.0.0 while we investigate and fix this.
Thanks for reporting this.
It looks to be caused by the dispatching to a dead handler, and trying to upgrade the lock.
This will be affecting 9.0.0 and 8.2.1, we've delisted both packages, and will be pushing a fix for it ASAP
This has been fixed in #514
And released to nuget under 9.0.1
Again, thanks for raising this, and sorry for nuisance this release caused for you.
No worries! Thanks for the quick fix!
Was the wrong version delisted here? On NuGet I'm seeing 8.2.1 still present but 8.2.0 seems to be gone, but I think it should be the other way around: https://www.nuget.org/packages/Mindscape.Raygun4Net.AspNetCore/8.2.1#versions-body-tab
We just mistakenly upgraded to 8.2.1 and hit this again as a result.
You're absolutely right @olane - thanks for the heads up.
I've delisted that package now, feel free to reach out if you run into any other issues when upgrading, cheers.
Just saw this exception when using Raygun4net, seems to be related to this file.