Skip to content
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

Ensure server port numbers are numeric and ensure they are stored as … #55

Merged
merged 1 commit into from
Jul 26, 2020

Conversation

wishdev
Copy link
Contributor

@wishdev wishdev commented Jul 26, 2020

…integers

When passing in a "0" for the port number - the port number is not updated as is the intention. Ensuring the port number is stored as an integer solves this.

@jeremyevans
Copy link
Contributor

Thanks for the patch! I agree that it makes sense to store the port as an integer.

@jeremyevans jeremyevans merged commit 86ed621 into ruby:master Jul 26, 2020
@wishdev wishdev deleted the port_number branch July 28, 2020 20:28
thesamesam added a commit to thesamesam/gentoo that referenced this pull request Apr 1, 2023
- Enable ruby32

- Fix tests

Fixing tests was interesting. I very quickly found the upstream
commits touching the port deduction/specification bit, but I had
no idea why this would've started failing on all Rubies all of a sudden
yet.

But ended up, after looking through MRI Ruby release notes,
figured out it must be somewhere else (it didn't seem to be a backported
bundled gem update).

It looks like it's actually because of a change in an (undeclared)
test dep - dev-ruby/webrick. It was probably ruby/webrick#55
or similar, but enough to satisfy my curiosity anyway.

Signed-off-by: Sam James <sam@gentoo.org>
thesamesam added a commit to thesamesam/gentoo that referenced this pull request Apr 1, 2023
- Enable ruby32

- Fix tests

Fixing tests was interesting. I very quickly found the upstream
commits touching the port deduction/specification bit, but I had
no idea why this would've started failing on all Rubies all of a sudden
yet.

But ended up, after looking through MRI Ruby release notes,
figured out it must be somewhere else (it didn't seem to be a backported
bundled gem update).

It looks like it's actually because of a change in an (undeclared)
test dep - dev-ruby/webrick. It was probably ruby/webrick#55
or similar, but enough to satisfy my curiosity anyway.

Signed-off-by: Sam James <sam@gentoo.org>
thesamesam added a commit to thesamesam/gentoo that referenced this pull request Apr 1, 2023
- Enable ruby32

- Fix tests

Fixing tests was interesting. I very quickly found the upstream
commits touching the port deduction/specification bit, but I had
no idea why this would've started failing on all Rubies all of a sudden
yet.

But ended up, after looking through MRI Ruby release notes,
figured out it must be somewhere else (it didn't seem to be a backported
bundled gem update).

It looks like it's actually because of a change in an (undeclared)
test dep - dev-ruby/webrick. It was probably ruby/webrick#55
or similar, but enough to satisfy my curiosity anyway.

Signed-off-by: Sam James <sam@gentoo.org>
gentoo-bot pushed a commit to gentoo/gentoo that referenced this pull request Apr 1, 2023
- Enable ruby32

- Fix tests

Fixing tests was interesting. I very quickly found the upstream
commits touching the port deduction/specification bit, but I had
no idea why this would've started failing on all Rubies all of a sudden
yet.

But ended up, after looking through MRI Ruby release notes,
figured out it must be somewhere else (it didn't seem to be a backported
bundled gem update).

It looks like it's actually because of a change in an (undeclared)
test dep - dev-ruby/webrick. It was probably ruby/webrick#55
or similar, but enough to satisfy my curiosity anyway.

Signed-off-by: Sam James <sam@gentoo.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants