Closed nickalbrecht closed 6 years ago
I'm not 100% positive it's Exceptional's problem since I'm not entirely sure I am reading the stack traces in ASP.NET Core correctly. But I think it is? lol
@nickalbrecht as far as I can tell, Exceptional is simply logging an error here, not causing one. Seems you're hitting an issue somewhere in System.Reflection.RuntimeAssembly
.
Hmmm, except that I'm not doing any reflecting. K, I'll look into this deeper next time it happens. Now that I'm looking at this again with fresh eyes, I think I see where I got mixed up. Thanks!
Getting a weird behavior with the Exceptional error handler. Soon as I restarted the app pool it went away.
No line numbers, so not sure where in the
LogAsync
it's happening.