There are apparently some nasty heap corruption issues with libxml-ruby
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- build-system
Research direction
Start by checking the Gemfile and the Bundler dependency resolution represented by Bundler.locked_gems. Confirm how libxml-ruby enters the locked specifications and use the issue's example as the expected check. Done means the resolved bundle does not include libxml-ruby alongside nokogiri.
Written by the indexing model from the issue text.
Description
describe 'Gemfile' do
it 'should not include libxml-ruby' do
libxml = Bundler.locked_gems.specs.detect { |s| s.name == 'libxml-ruby' }
expect(libxml).to be_nil, "libxml-ruby is incompatible with nokogiri and causes heap corruption"
end
- Dominant language
- Ruby
- Stars
- 51
- Forks
- 42
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 1
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.
More from testmycode/tmc-server
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
testmycode/tmc-server#590 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
testmycode/tmc-server#576 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
testmycode/tmc-server#488 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
testmycode/tmc-server#487 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
testmycode/tmc-server#477 · 2 comments ·
All issues in testmycode/tmc-server
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100