Future of (development) dependency for byebug?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 202
- Forks
- 27
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 1
Description
Currently for power_assert testsuite, it depends on byebug:
https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/power_assert.gemspec#L26
https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/test/trace_test.rb#L10
So can I rely on byebug?
Why I am asking here is that
- The last activity on https://github.com/deivid-rodriguez/byebug seems more than 2 years ago.
- And it seems that with ruby 3.3 (I tested https://github.com/ruby/ruby/commit/cd67c0d2040f1ade0fe8b1533816281553bfe6e6 ) byebug testsuite fails , and looks like byebug does not work with ruby 3.3 properly.
So I think if power_assert is going to use byebug, someone has to support byebug maintainership.
Or can power_assert be switched to use debug gem?
Contributor guide
No contributing guide indexed for this repository
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
Start with the dependency declaration in power_assert.gemspec at line 26 and the byebug usage in test/trace_test.rb at line 10. Check the reported Ruby 3.3 test failure and compare whether the existing suite can use the debug gem instead; done means an agreed, compatible dependency and passing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100