-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Describe the bug
TestMyCode: Initialization error during tmc-langs setup: Connection Error: fetch failed. Caused by: {Error: Client network socket disconnected before secure TLS connection was established. Error: Client network socket disconnected before secure TLS connection was established at TLSSocket.onConnectEnd (node:_tls_wrap:1732:19) at TLSSocket.emit (node:events:530:35) at endReadableNT (node:internal/streams/readable:1698:12) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) }. TypeError: fetch failed at e.exports.fetch (c:\Users\Zan.vscode\extensions\moocfi.test-my-code-3.4.0\dist\lib.js:2:421288) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async t.downloadFile (c:\Users\Zan.vscode\extensions\moocfi.test-my-code-3.4.0\dist\lib.js:2:536536) at async c:\Users\Zan.vscode\extensions\moocfi.test-my-code-3.4.0\dist\lib.js:2:245685 If this issue is not resolved, the extension may not func...
To Reproduce
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
If the reproduction includes opening a course or exercise, please include which course and/or exercise the issue can be reproduced with.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- VSCode Version [e.g. 1.4.0]
- TMC Extension Version [e.g. 0.8.1]
- Other related extensions.
TMC Extension logs
Note: To open VSCode's Command Palette, you can select View in the top bar followed by the Command Palette... option, or use a keyboard shortcut (Ctrl+Shift+P on Windows or Linux, ⇧⌘P on MacOS, or F1 on either by default).
- Open the Command Palette, type in
tmc.settingsand press Enter to open the extension settings. In the settings, make sure theLog Levelis set toVerbose. - Open the Command Palette, type in
tmc.debugand press Enter to open the extension logs. - Reproduce the error.
- Copy the extension logs that opened in step 2. and paste them here.
Additional context
Add any other context about the problem here.