Good morning everyone! Welcome to the Less-Common C# Keywords Tour here at Exception Not Found! My name is Reggie and I'll be your tour guide today. For those of you who are visiting us for the first time, welcome! For those of you who have taken our other tours [https:
A few weeks back I wrote about a very unusual bug that returned 500 errors for routes that should have been valid [https://www.exceptionnotfound.net/a-stupid-bug-and-a-plea-for-help/]. Recently my team and I, to our great relief, discovered the cause of this bug. Of course, that wasn't before we ended up
UPDATE (17 May 2017): We've fixed the stupid bug described in this post! Check it out [https://www.exceptionnotfound.net/solving-the-stupid-bug/]! Bug hunts can take on many forms. Some are simple cleanup jobs [https://www.exceptionnotfound.net/the-bug-is-in-your-code/], some take hours and end up being something stupid [https://www.exceptionnotfound.
The problems started small, as they often do. But as we've seen many times before [https://www.exceptionnotfound.net/how-do-you-fix-an-impossible-bug/], lots of small problems in quick succession tend to make one big problem. In this case, the problem got big fast. It started off easy enough: read the big report,
Within the span of an hour, it had all gone to hell. The first deployment went rather smoothly. It was a fix to an existing web service, and went out with no problems, or so we thought. Within ten minutes of the deployment, the users started complaining of a minor