Gracefully handle deprecation of io-wait gem

Open Beginner friendly
#218 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
ruby
Domain
backend

Research direction

Start at lib/webrick/httpserver.rb around line 12 and read the linked Ruby commit to understand the io-wait deprecation handling. Reproduce the ruby -r webrick command shown in the issue, then verify that requiring WEBrick no longer produces the reported deprecation warning while preserving the existing server behavior.

Written by the indexing model from the issue text.

Description

$ ruby -r webrick
The io-wait gem is deprecated; all functionality ships with Ruby 3.2 and higher.

https://github.com/ruby/webrick/blob/master/lib/webrick/httpserver.rb#L12
https://github.com/ruby/ruby/commit/fed732c8f4e4e9218bae7a2e5b142dc9b072a40e

Dominant language
Ruby
Stars
327
Forks
113
Avg merge
4h 2m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/webrick

All issues in ruby/webrick

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.