-
-
Notifications
You must be signed in to change notification settings - Fork 60
support for search options in /etc/resolv.conf #199
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
Closed
Closed
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
fa1684d
support for search options in /etc/resolv.conf
Chrisdowson 54ed2cf
1. fix test case and optimized code
Chrisdowson 1a1b72d
fix test case
Chrisdowson 0ba2010
fix test case
Chrisdowson 2202726
Merge branch '1.x' into 1.x
Chrisdowson 38c9526
1.revert
Chrisdowson 23cb5e6
Merge branch 'reactphp:1.x' into 1.x
Chrisdowson 8980bdd
1.fix bug
Chrisdowson b3e980a
Optimize code
Chrisdowson e675f09
Merge branch '1.x' into 1.x
Chrisdowson File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -535,7 +535,7 @@ public function testQueryRejectsWhenServerSendsInvalidMessage() | |
| $address = stream_socket_get_name($server, false); | ||
| $executor = new TcpTransportExecutor($address); | ||
|
|
||
| $query = new Query('google.com', Message::TYPE_A, Message::CLASS_IN); | ||
| $query = new Query('bing.com', Message::TYPE_A, Message::CLASS_IN); | ||
|
|
||
| $exception = null; | ||
| $executor->query($query)->then( | ||
|
|
@@ -552,7 +552,7 @@ function ($e) use (&$exception) { | |
|
|
||
| /** @var \RuntimeException $exception */ | ||
| $this->assertInstanceOf('RuntimeException', $exception); | ||
| $this->assertEquals('DNS query for google.com (A) failed: Invalid message received from DNS server tcp://' . $address, $exception->getMessage()); | ||
| $this->assertEquals('DNS query for bing.com (A) failed: Invalid message received from DNS server tcp://' . $address, $exception->getMessage()); | ||
| } | ||
|
|
||
| public function testQueryRejectsWhenServerSendsInvalidId() | ||
|
|
@@ -688,7 +688,7 @@ public function testQueryResolvesIfServerSendsValidResponse() | |
|
|
||
| $this->assertInstanceOf('React\Dns\Model\Message', $response); | ||
| } | ||
|
|
||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is a leftover. |
||
| public function testQueryRejectsIfSocketIsClosedAfterPreviousQueryThatWasStillPending() | ||
| { | ||
| $loop = $this->getMockBuilder('React\EventLoop\LoopInterface')->getMock(); | ||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see why we should change
google.comtobing.comhere, seems unnecessary. Same goes for the other tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In China,we can not visit google.com, so tests will not pass on my computer,But bing.com we can
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with you that we should use something that works for everyone, in some of our projects we started using
reactphp.orginstead, but I don't think this belongs in this pull request. Maybe usebing.comfor testing purposes on your system without committing it in the end.What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SimonFrings IMHO it makes sense to change everything to
reactphp.orgto align this across the board. Will file PoC PR for that to take this discussion there.@Chrisdowson I assume you can reacht
reactphp.orgjust fine?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes,I can reach
reactphp.orgThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with WyriHaximus, How about I replace
bing.comwithreactphp.orgnow?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@WyriHaximus @Chrisdowson I agree with both of you, I am not sure if this is something we should tackle in this pull request as it doesn't fit to the other changes made in here and could seem a bit random. It also keeps the diff significantly smaller and lays focus on the actual changes. That's the reason I suggest a (follow-up) pull request where we change
google.comtoreactphp.org.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SimonFrings @Chrisdowson just opened reactphp/event-loop#263 to kick off the discussion.