Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Running SSHKit tests with Rake 11.0 reveals many Ruby warnings

Open
#344 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
devops

Research direction

Start by running SSHKit's test suite with Rake 11.0 and Ruby warnings enabled, then inspect the warning locations named in lib/sshkit/runners/group.rb, lib/sshkit/host.rb, and lib/sshkit/backends/abstract.rb. Review the existing discussion before choosing whether the warnings should be fixed or suppressed; done means the project has a decided approach and the warning flood is addressed.

Written by the indexing model from the issue text.

Description

discuss!

Rake 11.0 turns on Ruby warnings by default. With warnings enabled, running SSHKit's test suite results in a flood of messages like this:

lib/sshkit/runners/group.rb:15: warning: instance variable @group_size not initialized
lib/sshkit/host.rb:59: warning: instance variable @local not initialized
lib/sshkit/backends/abstract.rb:141: warning: instance variable @pwd not initialized
lib/sshkit/backends/abstract.rb:149: warning: instance variable @env not initialized
lib/sshkit/backends/abstract.rb:149: warning: instance variable @user not initialized
lib/sshkit/backends/abstract.rb:149: warning: instance variable @group not initialized

We could:

  • Treat these warnings as legitimate and try to fix them; or
  • Turn off Ruby warnings

I haven't had time to think this through yet, so for now I'm just opening it for discussion.

Your thoughts?

Dominant language
Ruby
Stars
1.2k
Forks
257
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 capistrano/sshkit

All issues in capistrano/sshkit

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.