Stuck on an issue?
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.
ArgumentExceptions in FieldResolver bubble out as UnexpectedElasticsearchClientExceptions
See original GitHub issueThe underlying exception is an ArgumentException and it should bubble out as an ElasticsearchClientException. The problem lies in the fact that .Resolve() is called later in the pipeline.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Going to bump this for now and release 2.0.5 without it. It’s low priority anyway.
Closing, as I don’t think there’s anything actionable here. We can revisit again for 6.x if necessary.