Ignoring debug-1.7.1 because its extensions are not built
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the VSCode debugging-session startup on Ruby 2.7.6 and inspect the reported debug-1.7.1 and io-console-0.6.0 extension warnings. Check the gem installation or startup path involved; done means identifying a reproducible cause and confirming that the warnings no longer prevent a debugging session.
Written by the indexing model from the issue text.
Description
Get the following error when I try to start a new debugging session in VSCode
Ruby version is 2.7.6
Ignoring debug-1.7.1 because its extensions are not built. Try: gem pristine debug --version 1.7.1 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 because its extensions are not built. Try: gem pristine io-console --version 0.6.0 Ignoring io-console-0.6.0 bec
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
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 ruby/debug
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
バグ
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TheOdinProject/curriculum#31402 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100