+972 52-548-6969
Fixing a production issue
time to read 2 min | 246 words
So we had a problem in our production environment. It showed up like this.
The first thing that I did was log into our production server, and look at the logs for errors. This is part of the new operational features that we have, and it was a great time to try it under real world conditions:
This gave me a subscription to the log, which gave me the exact error in question:
From there, I went to look at the exact line of code causing the problem:
Can you see the issue?
We create a dictionary that was case sensitive, and they used that to create a dictionary that was case insensitive. The actual fix was adding the ignore case comparer to the group by clause, and then pushing to production.
Comments
.ToDictionary() did not throw such an exception while new ConcurrentDictionary did. The difference is that the later one is not case sensitive. Are there any collection names the same but with different cases?
Stephen, Yes, that was the problem
Comment preview