Fix InvalidAddressError message

[ishikawa999]

This pull request will fix issue #60.
Fix to use the addr variable that exists instead of the non-existent @addr.

[knu]

Good catch. Thanks!

[corrupt952]

@ishikawa999 @knu

What is the status of this PR?
It looks like 65a4c41 was merged last week, so if I re-checkout from master or merging master, the build that is failing on this PR appears to be ready to go through.

[knu]

The current status is CI failure left. As far as I recall, I approved this PR waiting for the tests to finish, and then some of them failed.

The failed actions cannot be rerun by now, so you'll have to push again to trigger a new run.

I guess Ruby 2.4 & 2.5 on macOS may be removed if they still fail again because those versions are too old.

[melroy89]

LGTM

[taketo1113]

The current status is CI failure left. As far as I recall, I approved this PR waiting for the tests to finish, and then some of them failed.

The failed actions cannot be rerun by now, so you'll have to push again to trigger a new run.

I guess Ruby 2.4 & 2.5 on macOS may be removed if they still fail again because those versions are too old.

The errors on Ruby 2.4 & 2.5 on macOS have already been fixed in the following PR:

• CI: use macos-13 for Ruby 2.4, 2.5 #74
• CI: Builds fail due to 2.4, 2.5 can't run latest macOS #73

It seems that rebasing this branch should resolve the errors.

@ishikawa999 Could you please rebase it?

Reference

I tried rebasing on my forked repository, and the CI passed:
https://github.com/taketo1113/ipaddr/actions/runs/18406167879

(Resolved by test-unit-ruby-core gem v1.0.10) However, since the test-unit-ruby-core gem v1.0.9 causes errors on Ruby 2.4 and earlier, this CI run pins the gem to v1.0.7.
This issue has already been fixed in the following PR, and it's expected to be resolved in the next release (1.0.10?) of the test-unit-ruby-core gem:

• Fix SyntaxError: unexpected keyword_rescue, expecting keyword_end in Ruby 2.4 and earlier test-unit-ruby-core#18

[ishikawa999]

Thanks for the review, and sorry I missed your feedback earlier.
@taketo1113 I’ve rebased the branch; does it look okay now?

[taketo1113]

@ishikawa999 Thank you for your response.

The CI for ruby/ipaddr hasn’t run yet, but since the CI for ishikawa999/ipaddr is all green, I think it should be fine.
https://github.com/ishikawa999/ipaddr/actions/runs/18582133324

@knu @hsbt The CI will pass, so could you please check it?

The current status is CI failure left. As far as I recall, I approved this PR waiting for the tests to finish, and then some of them failed.
#70 (comment)

[taketo1113]

@hsbt Thank you for merging.
I'm glad because this is the fix I wanted to use.