Ruby 3.4 usage issues warning
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 133
- Forks
- 73
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 2
Description
Version:
Found this issue with both 3.3.6 and 3.3.8 ( latest )
Environment:
Using this with InSpec and Ruby 3.4.1 on a mac operating system.
Scenario:
Found the issue while running the test suite of InSpec with the following command bundle exec rake test TEST="test/functional/inspec_exec_json_test.rb".
It throws continuous warnings when upgrading Ruby version on 3.4.1 with this gem.
Please ignore the minitest warning, and only look at the one getting from mixlib-shellout.
Steps to Reproduce:
Simply using this gem with Ruby 3.4 should throw this warning.
Expected Result:
To modify the gem as per the warning.
Actual Result:
A warning being thrown with warning: literal string will be frozen in the future.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the warning with Ruby 3.4.1 using bundle exec rake test TEST="test/functional/inspec_exec_json_test.rb" in InSpec, focusing on the warning attributed to mixlib-shellout rather than the minitest warning. Trace the warning to the gem code and update the affected usage so the test run no longer emits literal string will be frozen in the future.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100