fix(endpoint): use custom resolver if specified for [IP] tests #1081
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ishanjain28
force-pushed
the
use_custom_resolver
branch
from
5ced376 to
5087627
Compare
TwiN
reviewed
May 24, 2025
TwiN
reviewed
May 24, 2025
|
@TwiN I addressed the PR feedback and it is ready for review again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes #904
It updates the endpoint code to resolve a domain with the specified custom resolver if specified or go to the default resolver as fallback
No documentation changes are required since this fixes a bug
Checklist
README.md, if applicable.