Initializing the extension failed TMC
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript, vscode
- Domain
- devtools
Research direction
Start by tracing extension initialization and the downloadFile call named in the stack trace; the reported failure is fetching tmc-langs with a self-signed certificate in the chain. Check whether it can be reproduced with the reported proxy, firewall, or antivirus conditions. Done should mean the initialization failure is understood and the extension handles the reported case appropriately.
Written by the indexing model from the issue text.
Description
Initializing the extension failed
Something went wrong while initializing the extension.
Failed to initialize tmc-langs: fetch failed: Error: self signed certificate in certificate chain. Stack trace: TypeError: fetch failed at e.exports.fetch (c:\Users\tirufire.aberra.vscode\extensions\moocfi.test-my-code-3.5.4\dist\lib.js:2:386233) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async t.downloadFile (c:\Users\tirufire.aberra.vscode\extensions\moocfi.test-my-code-3.5.4\dist\lib.js:2:485774) at async c:\Users\tirufire.aberra.vscode\extensions\moocfi.test-my-code-3.5.4\dist\lib.js:2:222168
This error may be caused by a proxy or firewall that is blocking network requests or by an antivirus program. This may also be caused by an antivirus program. You can try to resolve this issue by adding an exception to the directory at 'c:\Users\tirufire.aberra\AppData\Roaming\Code\User\globalStorage\moocfi.test-my-code\cli'.
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 8
- Avg merge
- 19m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 rage/tmc-vscode
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
rage/tmc-vscode#784 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
rage/tmc-vscode#781 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
rage/tmc-vscode#779 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rage/tmc-vscode#777 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rage/tmc-vscode#776 · 1 comment ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#33947 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paperclipai/paperclip#20942 ·
Maintainers usually reply within 1 day
-
area: documentation good first issue package: rule-data status: accepting prs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mastra-ai/mastra#30109 · 2 comments ·
Maintainers usually reply within 1 day