Fix the exception handling for cases where socket.gaierror is thrown.#579
Open
heri3x wants to merge 1 commit intoAirtestProject:masterfrom
Open
Fix the exception handling for cases where socket.gaierror is thrown.#579heri3x wants to merge 1 commit intoAirtestProject:masterfrom
heri3x wants to merge 1 commit intoAirtestProject:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I encountered an issue where the line "ip = self.device.get_ip_address()" was throwing a socket.gaierror exception and not being handled properly, causing the program to exit.
And I fixed this problem.
By the way, it seems that the socket.gaierror exception occurs in a Windows environment when a DNS suffix is set and the "Use this connection's DNS suffix in DNS registration" option is not checked in the network connection. Checking the "Use this connection's DNS suffix in DNS registration" option will prevent this issue from occurring.
Environment: