This repository has been archived by the owner on Oct 18, 2021. It is now read-only.
Resolve weird issues looking up addresses by switching interfaceIndex to the proper type #7
Conversation
This file contains 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
…o the proper type
|
Huh, interesting. Definitely looks like a good change since the DNS API uses a uint32_t. |
snej
added a commit
that referenced
this pull request
Jul 9, 2013
Resolve weird issues looking up addresses by switching interfaceIndex to the proper type
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolve weird issues looking up addresses by switching interfaceIndex to the proper type.
I'm not sure why this was suddenly causing issues in my app, it used to work - maybe an OS update or something, but interfaceIndex was coming in as -1, which got changed to what I'm assuming was no longer a sentinal value when the type got squashed.