Fix exception attribute outputs undefined method '=~' for false
when Net::Ping::External#ping6
succeeds
#39
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.
This Pull Request fixes an issue where an
undefined method '=~' for false
error is output to the exception attribute whenNet::Ping::External#ping6
succeeds.Steps to reproduce
Expected behavior
When
Net::Ping::External#ping6
succeeds, theexception
attribute should benil
, similar to how it behaves withNet::Ping::External#ping
.Actual behavior
When
Net::Ping::External#ping6
succeeds, theexception
attribute is notnil
and instead has the valueundefined method '=~' for false
.