Update puma: 5.1.1 → 5.2.1 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ puma (5.1.1 → 5.2.1) · Repo · Changelog

Release Notes

5.2.1

2021-02-05

• Bugfixes
  • Fix TCP cork/uncork operations to work with ssl clients ([#2550])
  • Require rack/common_logger explicitly if :verbose is true ([#2547])
  • MiniSSL::Socket#write - use data.byteslice(wrote..-1) ([#2543])
  • Set @env[CONTENT_LENGTH] value as string. ([#2549])

5.2.0

• Features

  • 10x latency improvement for MRI on ssl connections by reducing overhead ([#2519])
  • Add option to specify the desired IO selector backend for libev ([#2522])
  • Add ability to set OpenSSL verification flags (MRI only) ([#2490])
  • Uses flush after writing messages to avoid mutating $stdout and $stderr using sync=true ([#2486])

• Bugfixes

  • MiniSSL - Update dhparam to 2048 bit for use with SSL_CTX_set_tmp_dh ([#2535])
  • Change 'Goodbye!' message to be output after listeners are closed ([#2529])
  • Fix ssl bind logging with 0.0.0.0 and localhost ([#2533])
  • Fix compiler warnings, but skipped warnings related to ragel state machine generated code ([#1953])
  • Fix phased restart errors related to nio4r gem when using the Puma control server ([#2516])
  • Add #string method to Puma::NullIO ([#2520])
  • Fix binding via Rack handler to IPv6 addresses ([#2521])

• Refactor

  • Refactor MiniSSL::Context on MRI, fix MiniSSL::Socket#write ([#2519])
  • Remove Server#read_body ([#2531])
  • Fail build if compiling extensions raises warnings on GH Actions, configurable via MAKE_WARNINGS_INTO_ERRORS ([#1953])

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ nio4r (indirect, 2.5.4 → 2.5.5) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 14 commits:

• Patch version bump.
• Be more explicit with why `pure?` is being used.
• Workaround for ARM-based macOS bundled Ruby
• Allow pure Ruby and Java NIO::Selector to be initialized with nil
• Declare linuxaio and io_uring experimental
• linuxaio is actually only supported on linux kernel 4.19+
• Define EV_USE_IOURING if header is present
• Patch libev and add support for linuxaio and io_uring
• Upgrade libev to verion 4.33
• Add ruby 3.0 to the README
• Add ruby 3.0 to the CI pipeline
• Actions - add MRI head/master for Ubuntu & macOS
• Update Actions workflow - OS changes & additions
• Fix javac -Xlint warnings

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #294.