Skip to content

Fail discovery when custom resolver fails #533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 1, 2018

Conversation

lutovich
Copy link
Contributor

It is better to surface the resolution error instead of silently using the address as-is. Also added stub server tests for custom address resolver.

It is better to surface the resolution error instead of silently using
the address as-is. Also added stub server tests for custom address
resolver.
@lutovich lutovich requested a review from zhenlineo September 28, 2018 13:11
@zhenlineo zhenlineo merged commit d6f1f86 into neo4j:1.7 Oct 1, 2018
@lutovich lutovich deleted the 1.7-resolver-throws branch October 7, 2018 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants