Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Exception message thrown by SingleAsync, when sequence contains no element, is vague
See original GitHub issueEntity Framework Core’s extension method SingleAsync throws an exception, if more than one element exists. The message of this exception is vague and does not match with it’s synchronous LINQ counterpart Single.
For comparison this is the message for the exception that is thrown by the Single method.
System.InvalidOperationException: Sequence contains more than one matching element.
And here the exception message thrown by SingleAsync, which doesn’t really tell us what the actual problem is:
System.InvalidOperationException: ‘Enumerator failed to MoveNextAsync.’
Expectation: The exception messages should be equal for both the synchronous and the asynchronous version.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:32
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ajcvickers The message returned is correct in ef core 2.2. This is only happening in ef core 3.0. The entire stack strace is changed. May be this should be considered a bug rather than enhancement.
The same happens with
FirstAsync, when no element is returned.