Open azazar opened 9 months ago
File 8-Continue - LLM PromptCompletion.log
is empty when it's crashing.
Pre-release version crashed with the same error. But latest version is working just fine in older VSCode release on the same machine:
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:19.222Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 6.1.0-18-amd64
I get this problem on linux with any version of vscode. But it was working until a recent update. It does not matter which version of vscode I downgrade to. However if I downgrade to version 0.8.0 of Continue it is fine. It seems to start indexing and then never finish. Maybe the repo is too big or there is no file write primitive somewhere. Still working on the macpro. I don't think it is cached settings. I removed the dotfolder.
Glad to see it's not just me seeing this error. I'm seeing this when using the code-server Docker container from LinuxServer.io (linuxserver/mods:code-server-python3), which looks to be running on Ubuntu 22.04. Changing the version of the extension installed to 0.8.0 works. I've tried deleting and recreating the container, and even start it without any repo loaded, but this error appears almost instantly. It would be great to understand why this is happening so I can benefit from using the latest version.
Strangely, on my Debian 12 desktop at home, I've never seen this issue. It's currently using the latest release version of Continue (0.8.17).
@kingprawn22 @nf3xn @azazar my first thought here is that it's related to indexing taking up resources when calculating embeddings. I'm planning to do some profiling in the next couple of days on really large repos to check performance, but does it seem like a pattern that this only happens on large codebases? I actually wouldn't be surprised if this was at the intersection of a) large codebase and b) non-local setup (e.g. Remote SSH, WSL, etc.)
@sestinj Maybe my issue is slightly different in that case. Even with a completely empty workspace, I see this error as soon as I click on the Continue extension. It offers to restart the 'Remote Extension Host', but the error appears again shortly after.
I see. This must be different then. I suspect there might be logs that show the full problem if you do cmd/ctrl+shift+p, "Toggle Developer Tools", and then look in the console
Since I'm using code-server in the browser, I just used F12 to view the dev tools. Here's the output that appears when the extension tries to load:
INFO Creating a socket (renderer-ExtensionHost-596c7b59-1b4b-4ce5-abfe-58fff46360ff)... [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
INFO Creating a socket (renderer-ExtensionHost-596c7b59-1b4b-4ce5-abfe-58fff46360ff) was successful after 36 ms. [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [webviewElement.ts:441:10](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/contrib/webview/browser/webviewElement.ts)
Feature Policy: Skipping unsupported feature name “autoplay”. [webviewElement.ts:441:10](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/contrib/webview/browser/webviewElement.ts)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [webviewElement.ts:511:10](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/contrib/webview/browser/webviewElement.ts)
Feature Policy: Skipping unsupported feature name “autoplay”. [webviewElement.ts:511:10](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/contrib/webview/browser/webviewElement.ts)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [webviewElement.ts:485:16](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/contrib/webview/browser/webviewElement.ts)
Feature Policy: Skipping unsupported feature name “autoplay”. [webviewElement.ts:485:16](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/contrib/webview/browser/webviewElement.ts)
[Extension Host] Error calling Ollama /api/show endpoint: TypeError: fetch failed 3 [console.ts:137:34](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/base/common/console.ts)
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. [code.awoc.xyz](https://code.awoc.xyz/?folder=/config/workspace/qobuz_scrape)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [index-no-csp.html:1002:13](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “autoplay”. [index-no-csp.html:1002:13](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [index-no-csp.html:1011:48](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “autoplay”. [index-no-csp.html:1011:48](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [index-no-csp.html:1014:18](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “autoplay”. [index-no-csp.html:1014:18](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [index-no-csp.html:1002:13](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “autoplay”. [index-no-csp.html:1002:13](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [index-no-csp.html:1011:48](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “autoplay”. [index-no-csp.html:1011:48](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [index-no-csp.html:1014:18](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Feature Policy: Skipping unsupported feature name “autoplay”. [index-no-csp.html:1014:18](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/contrib/webview/browser/pre/index-no-csp.html?id=ecf8d97a-1bc9-4c0c-afb2-adc5b9d6d0b5&origin=4366698e-5853-42e5-9131-939ac5f1468e&swVersion=4&extensionId=Continue.continue&platform=browser&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=https%3A%2F%2Fcode.awoc.xyz&remoteAuthority=code.awoc.xyz&purpose=webviewView)
Some cookies are misusing the recommended “SameSite“ attribute 3
Cookie “dmn_chk_018e2a5e-8ce6-7ed2-8394-a13df0773d6e” has been rejected for invalid domain. [index.js:704:23072](https://vscode-remote+code-002eawoc-002exyz.vscode-resource.vscode-cdn.net/config/extensions/continue.continue-0.8.17-linux-x64/gui/assets/index.js)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.posthog.com/e/?ip=1&_=1710107823339&ver=1.105.9. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.posthog.com/e/?ip=1&_=1710107823342&ver=1.105.9. (Reason: CORS request did not succeed). Status code: (null).
INFO [remote-connection][ExtensionHost][596c7…][reconnect] received socket close event (wasClean: false, code: 1006, reason: ). [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
ERR
close { target: WebSocket, isTrusted: true, wasClean: false, code: 1006, reason: "", srcElement: WebSocket, currentTarget: WebSocket, eventPhase: 2, bubbles: false, cancelable: false, … }
[log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
INFO [remote-connection][ExtensionHost][596c7…][reconnect] starting reconnecting loop. You can get more information with the trace log level. [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
INFO [remote-connection][ExtensionHost][596c7…][reconnect] resolving connection... [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
INFO [remote-connection][ExtensionHost][596c7…][reconnect] connecting to WebSocket(code.awoc.xyz:443)... [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
INFO Creating a socket (renderer-ExtensionHost-596c7b59-1b4b-4ce5-abfe-58fff46360ff)... [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
INFO Creating a socket (renderer-ExtensionHost-596c7b59-1b4b-4ce5-abfe-58fff46360ff) was successful after 436 ms. [log.ts:417:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
ERR [remote-connection][ExtensionHost][596c7…][reconnect][WebSocket(code.awoc.xyz:443)] received error control message when negotiating connection. Error: [log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
ERR Error: Connection error: Unknown reconnection token (seen before)
V remoteAgentConnection.ts:783
f remoteAgentConnection.ts:326
y event.ts:1127
fire event.ts:1158
fire ipc.net.ts:650
z ipc.net.ts:1021
beginAcceptReconnection ipc.net.ts:955
y event.ts:1127
fire event.ts:1158
acceptChunk ipc.net.ts:394
c ipc.net.ts:350
onData browserSocketFactory.ts:231
y event.ts:1127
fire event.ts:1158
onload browserSocketFactory.ts:92
S browserSocketFactory.ts:87
create browserSocketFactory.ts:204
connect browserSocketFactory.ts:285
connect browserSocketFactory.ts:282
connect remoteSocketFactoryService.ts:58
s remoteAgentConnection.ts:191
b remoteAgentConnection.ts:235
f remoteAgentConnection.ts:322
l remoteAgentConnection.ts:362
G remoteAgentConnection.ts:766
z remoteAgentConnection.ts:666
y remoteAgentConnection.ts:626
W remoteAgentConnection.ts:593
y event.ts:1127
z event.ts:1138
fire event.ts:1162
fire ipc.net.ts:650
f ipc.net.ts:876
c browserSocketFactory.ts:236
y event.ts:1127
fire event.ts:1158
S browserSocketFactory.ts:175
d dom.ts:143
o dom.ts:164
S browserSocketFactory.ts:152
create browserSocketFactory.ts:204
connect browserSocketFactory.ts:285
connect browserSocketFactory.ts:282
connect remoteSocketFactoryService.ts:58
s remoteAgentConnection.ts:191
b remoteAgentConnection.ts:235
f remoteAgentConnection.ts:322
l remoteAgentConnection.ts:362
L remoteAgentConnection.ts:428
M remoteAgentConnection.ts:444
L remoteAgentConnection.ts:425
start remoteExtensionHost.ts:125
promise callback*start remoteExtensionHost.ts:101
r extensionHostManager.ts:117
j instantiationService.ts:119
createInstance instantiationService.ts:85
wb abstractExtensionService.ts:774
vb abstractExtensionService.ts:754
ub abstractExtensionService.ts:741
run abstractExtensionService.ts:841
o notifications.ts:758
run actions.ts:158
u actions.ts:194
u notificationsCommands.ts:387
run actions.ts:185
[log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
ERR [remote-connection][ExtensionHost][596c7…][reconnect] A permanent error occurred in the reconnecting loop! Will give up now! Error: [log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
ERR Error: Connection error: Unknown reconnection token (seen before)
V remoteAgentConnection.ts:783
f remoteAgentConnection.ts:326
y event.ts:1127
fire event.ts:1158
fire ipc.net.ts:650
z ipc.net.ts:1021
beginAcceptReconnection ipc.net.ts:955
y event.ts:1127
fire event.ts:1158
acceptChunk ipc.net.ts:394
c ipc.net.ts:350
onData browserSocketFactory.ts:231
y event.ts:1127
fire event.ts:1158
onload browserSocketFactory.ts:92
S browserSocketFactory.ts:87
create browserSocketFactory.ts:204
connect browserSocketFactory.ts:285
connect browserSocketFactory.ts:282
connect remoteSocketFactoryService.ts:58
s remoteAgentConnection.ts:191
b remoteAgentConnection.ts:235
f remoteAgentConnection.ts:322
l remoteAgentConnection.ts:362
G remoteAgentConnection.ts:766
z remoteAgentConnection.ts:666
y remoteAgentConnection.ts:626
W remoteAgentConnection.ts:593
y event.ts:1127
z event.ts:1138
fire event.ts:1162
fire ipc.net.ts:650
f ipc.net.ts:876
c browserSocketFactory.ts:236
y event.ts:1127
fire event.ts:1158
S browserSocketFactory.ts:175
d dom.ts:143
o dom.ts:164
S browserSocketFactory.ts:152
create browserSocketFactory.ts:204
connect browserSocketFactory.ts:285
connect browserSocketFactory.ts:282
connect remoteSocketFactoryService.ts:58
s remoteAgentConnection.ts:191
b remoteAgentConnection.ts:235
f remoteAgentConnection.ts:322
l remoteAgentConnection.ts:362
L remoteAgentConnection.ts:428
M remoteAgentConnection.ts:444
L remoteAgentConnection.ts:425
start remoteExtensionHost.ts:125
promise callback*start remoteExtensionHost.ts:101
r extensionHostManager.ts:117
j instantiationService.ts:119
createInstance instantiationService.ts:85
wb abstractExtensionService.ts:774
vb abstractExtensionService.ts:754
ub abstractExtensionService.ts:741
run abstractExtensionService.ts:841
o notifications.ts:758
run actions.ts:158
u actions.ts:194
u notificationsCommands.ts:387
run actions.ts:185
[log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
Extension host (Remote) terminated unexpectedly. Code: 0, Signal: 596c7b59-1b4b-4ce5-abfe-58fff46360ff [abstractExtensionService.ts:790:10](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/workbench/services/extensions/common/abstractExtensionService.ts)
ERR Extension host (Remote) terminated unexpectedly with code null. [log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
ERR Extension host (Remote) terminated unexpectedly. The following extensions were running: vscode.emmet, vscode.git-base, vscode.git, vscode.github, vscode.debug-auto-launch, vscode.merge-conflict, Continue.continue, vscode.tunnel-forwarding [log.ts:437:12](https://code.awoc.xyz/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/out-vscode-reh-web/vs/workbench/file:/home/runner/work/code-server/code-server/lib/vscode/src/vs/platform/log/common/log.ts)
Remote Extension host terminated unexpectedly 3 times within the last 5 minutes.
It takes about a minute to crash when I run latest version in DevContainer.
While looking at output I noticed that it offers to generate a code in the output window.
Freshly installed VSCodium is crashing too.
Version: 1.87.2
Release: 24072
Commit: f7ed6417a7cfae92f98129384c13b505bb9cfc53
Date: 2024-03-12T18:30:28.994Z
Electron: 27.3.2
ElectronBuildId: undefined
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 6.1.0-18-amd64
I've updated to Continue v0.8.23 in my code-server container (linuxserver/vscodium) and it looks to be working for me now. No more 'remote host' errors.
code-server: v4.22.1 Code: 1.87.2
The issue has returned with v0.8.24. Downgrading to v0.8.23 still works.
Issue returned.
Ext. version: 0.8.24
VSCodium:
Version: 1.88.1
Release: 24102
Commit: f81c3ddb8c04073b36844c4102c939c634b770f5
Date: 2024-04-11T18:30:34.468Z
Electron: 28.2.8
ElectronBuildId: undefined
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.1.0-20-amd64
same Issue .
Ext. version: 0.8.20 -> 0.8.24 and pre-release.
VSCode:
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:34:12.840Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.5.0-28-generic
Looks like it's a Linux-only issue.
No! I'm facing this issue on Windows starting from issue creating date. Using WSL remote for full time past several years.
On Linux, I moved everything aside and started over (installing only continue ) and it failed with no project open after a few minutes. Current release.
Something like this:
mkdir foo; cd foo
mv ~/.vscode .
mv ~/.vscode-server .
mv ~/.config/Code .
Start code, add extension
$ code --list-extensions --show-versions
continue.continue@0.8.25
@azazar @kingprawn22 @mroark1m @serjs @annymosse Do all of you have "embeddingsProvider": { "name": "transformers.js" }
in your config.json? This would at least help scope the problem down to being related to the embeddings model
I did not have that in my config.json, but nothing changes after adding it. The issue exists on v0.8.24 and v0.8.25, so I downgrade to v0.8.23 which works.
those so many problems to investigate hosts
I'm using
VSCodium Version: 1.88.1 Release: 24104 Commit: 0d01a72525276e5e3771fe5851b9c83de0de1e2b Date: 2024-04-13T01:53:59.491Z Electron: 28.2.8 ElectronBuildId: undefined Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Linux x64 5.15.0-105-generic
on Ubuntu 22.04, with the following config:
{
"models": [
{
"title": "Llama 3",
"provider": "ollama",
"model": "llama3:8b-instruct-q8_0"
},
{
"title": "Ollama",
"provider": "ollama",
"model": "AUTODETECT"
}
],
"customCommands": [
{
"name": "test",
"prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
"description": "Write unit tests for highlighted code"
}
],
"tabAutocompleteModel": {
"title": "CodeQwen 15b",
"provider": "ollama",
"model": "codeqwen:7b-chat-v1.5-q8_0"
},
"allowAnonymousTelemetry": false,
"contextProviders": [
{
"name": "code",
"params": {}
},
{
"name": "docs",
"params": {}
}
],
"embeddingsProvider": {
"provider": "transformers.js"
}
}
With Continue v. 0.8.26 (as well as with the prerelease version) the crash is happening, but downgrading to 0.8.23 makes it go away.
What's interesting is that when I installed 0.8.26 I got the setup screen in the left sidebar, but I did not get the tutorial (continue_tutorial.py). I only got the tutorial after I installed 0.8.23. I didn't get the tutorial with the prerelease version either.
This is what I see in the Dev Console when upgrading from 0.8.23 to 0.8.27:
workbench.desktop.main.js:152 [Extension Host] Reinitialized extension settings
workbench.desktop.main.js:656 INFO Started local extension host with pid 2090502.
workbench.desktop.main.js:656 ERR No registered selector for ID: ms-vscode.npm-command
workbench.desktop.main.js:152 [Extension Host] Added a "Run Ansible Playbook" command...
workbench.desktop.main.js:152 [Extension Host] Added a "Run with Ansible Navigator" command...
workbench.desktop.main.js:152 [Extension Host] tox doc path: tasks -> .
workbench.desktop.main.js:2939 Extension host (LocalProcess pid: 2090502) terminated unexpectedly. Code: 0, Signal: unknown
_onExtensionHostCrashed @ workbench.desktop.main.js:2939
_onExtensionHostCrashed @ workbench.desktop.main.js:2940
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:2939
(anonymous) @ workbench.desktop.main.js:2939
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
_onExtHostProcessExit @ workbench.desktop.main.js:1654
(anonymous) @ workbench.desktop.main.js:1654
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
ce @ workbench.desktop.main.js:629
onResponse @ workbench.desktop.main.js:629
onBuffer @ workbench.desktop.main.js:629
(anonymous) @ workbench.desktop.main.js:628
_deliver @ workbench.desktop.main.js:89
_deliverQueue @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
fe @ workbench.desktop.main.js:85
emit @ VM20 sandbox_bundle:2
onMessage @ VM20 sandbox_bundle:2
workbench.desktop.main.js:656 ERR Extension host (LocalProcess pid: 2090502) terminated unexpectedly. No extensions were activated.
workbench.desktop.main.js:656 INFO Automatically restarting the extension host.
workbench.desktop.main.js:656 INFO Started local extension host with pid 2090737.
workbench.desktop.main.js:656 ERR No registered selector for ID: ms-vscode.npm-command
workbench.desktop.main.js:152 [Extension Host] Added a "Run Ansible Playbook" command...
workbench.desktop.main.js:152 [Extension Host] Added a "Run with Ansible Navigator" command...
workbench.desktop.main.js:152 [Extension Host] tox doc path: tasks -> .
workbench.desktop.main.js:2939 Extension host (LocalProcess pid: 2090737) terminated unexpectedly. Code: 132, Signal: unknown
_onExtensionHostCrashed @ workbench.desktop.main.js:2939
_onExtensionHostCrashed @ workbench.desktop.main.js:2940
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:2939
(anonymous) @ workbench.desktop.main.js:2939
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
_onExtHostProcessExit @ workbench.desktop.main.js:1654
(anonymous) @ workbench.desktop.main.js:1654
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
ce @ workbench.desktop.main.js:629
onResponse @ workbench.desktop.main.js:629
onBuffer @ workbench.desktop.main.js:629
(anonymous) @ workbench.desktop.main.js:628
_deliver @ workbench.desktop.main.js:89
_deliverQueue @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
fe @ workbench.desktop.main.js:85
emit @ VM20 sandbox_bundle:2
onMessage @ VM20 sandbox_bundle:2
workbench.desktop.main.js:656 ERR Extension host (LocalProcess pid: 2090737) terminated unexpectedly. No extensions were activated.
workbench.desktop.main.js:656 INFO Automatically restarting the extension host.
workbench.desktop.main.js:656 INFO Started local extension host with pid 2090952.
workbench.desktop.main.js:656 ERR No registered selector for ID: ms-vscode.npm-command
workbench.desktop.main.js:152 [Extension Host] Added a "Run Ansible Playbook" command...
workbench.desktop.main.js:152 [Extension Host] Added a "Run with Ansible Navigator" command...
workbench.desktop.main.js:152 [Extension Host] tox ansible no active editor found
workbench.desktop.main.js:152 [Extension Host] Workspace root directory: /home/shock/src/ansible-nas
workbench.desktop.main.js:2939 Extension host (LocalProcess pid: 2090952) terminated unexpectedly. Code: 0, Signal: unknown
_onExtensionHostCrashed @ workbench.desktop.main.js:2939
_onExtensionHostCrashed @ workbench.desktop.main.js:2940
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:2939
(anonymous) @ workbench.desktop.main.js:2939
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
_onExtHostProcessExit @ workbench.desktop.main.js:1654
(anonymous) @ workbench.desktop.main.js:1654
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
ce @ workbench.desktop.main.js:629
onResponse @ workbench.desktop.main.js:629
onBuffer @ workbench.desktop.main.js:629
(anonymous) @ workbench.desktop.main.js:628
_deliver @ workbench.desktop.main.js:89
_deliverQueue @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
fe @ workbench.desktop.main.js:85
emit @ VM20 sandbox_bundle:2
onMessage @ VM20 sandbox_bundle:2
workbench.desktop.main.js:656 ERR Extension host (LocalProcess pid: 2090952) terminated unexpectedly. No extensions were activated.
workbench.desktop.main.js:796 Extension host terminated unexpectedly 3 times within the last 5 minutes.
onDidChangeNotification @ workbench.desktop.main.js:796
(anonymous) @ workbench.desktop.main.js:796
_deliver @ workbench.desktop.main.js:89
_deliverQueue @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
addNotification @ workbench.desktop.main.js:796
notify @ workbench.desktop.main.js:1673
prompt @ workbench.desktop.main.js:1673
_onExtensionHostCrashed @ workbench.desktop.main.js:2940
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:2939
(anonymous) @ workbench.desktop.main.js:2939
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
_onExtHostProcessExit @ workbench.desktop.main.js:1654
(anonymous) @ workbench.desktop.main.js:1654
_deliver @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
ce @ workbench.desktop.main.js:629
onResponse @ workbench.desktop.main.js:629
onBuffer @ workbench.desktop.main.js:629
(anonymous) @ workbench.desktop.main.js:628
_deliver @ workbench.desktop.main.js:89
_deliverQueue @ workbench.desktop.main.js:89
fire @ workbench.desktop.main.js:89
fe @ workbench.desktop.main.js:85
emit @ VM20 sandbox_bundle:2
onMessage @ VM20 sandbox_bundle:2
I'm having the same issue with a linux box.
Here is some of my details of the situation from my side:
This is what I can recall off the top of my mind right now. I'm a bit busy, and when I have a better chance, I can generate some crash logs for this thread. (Web dev tools, vscode output logs, continue configs, etc.)
I have the same problem on my Gentoo with VSCode 1.91.1 with Continue v0.8.43 and v0.9.189, but it happened only on a big Unity repository, with both the default embeddingsProvider
and ollama
Version 0.8.23 works
Extension host was not restarting with indexing disabled on 0.8.44, but it's now restarting again after I updated to 0.8.45.
Extension host was not restarting with indexing disabled on 0.8.44, but it's now restarting again after I updated to 0.8.45.
Confirmed. Was working on my end with indexing enabled on 0.8.44, 0.8.45 reintroduced the problem. It's reproducible, when you downgrade to 0.8.44 everything is working.
Extension host was not restarting with indexing disabled on 0.8.44, but it's now restarting again after I updated to 0.8.45.
Confirmed. Was working on my end with indexing enabled on 0.8.44, 0.8.45 reintroduced the problem. It's reproducible, when you downgrade to 0.8.44 everything is working.
Same. Had to downgrade
I have the same problem running on code-server. Downgrading to 0.8.44 with indexing disabled or to 0.8.11 with indexing enabled resolve the matter. So my guess is that this issue started from 0.8.12 related to indexing and that since 0.8.45, disableIndexing
set to true
doesn't seem to be processed anymore.
@azazar can you share the exact dev container configuration (or as close to what you can share publicly), as well as the code in the repository (or something representative, or a high-level description including rough file count if you can't share), and your OS? Using a dev container seems like the best chance to reproduce this
I have vscode 1.93.1 with Version: 0.8.52 on two x86 Ubuntu 24.04.1 machines. It works on one of two. On the machine it does not work ( even with 0.8.44), I installed python packages from MS. Both installs are pretty new and basic, one file to test python things. Even if I disable all extensions, the extension host crashes because of continue.
The console log says:
ERR Extension host (LocalProcess pid: 38932) terminated unexpectedly. The following extensions were running: vscode.emmet, vscode.git-base, vscode.git, vscode.github, vscode.debug-auto-launch, vscode.merge-conflict, Continue.continue, vscode.markdown-language-features, vscode.extension-editing, vscode.markdown-math, vscode.configuration-editing, vscode.json-language-features, vscode.typescript-language-features, vscode.npm
Please let me know how to help debugging.
See https://github.com/twinnydotdev/twinny/issues/319 for a possible cause.
I believe this is caused by https://github.com/lancedb/lance/issues/2195 https://github.com/lancedb/lancedb/issues/1437.
I don't have AVX2 on my main dev machine. Any chance for a workaround?
I don't have AVX2 too. It's likely the cause then.
Same, this problem happened to me in a workstation with a Xeon X5675 that lacks AVX2 support... had similar problems in the past with some PyTorch builds so I guess the only solution is to recompile with a different target (?)
@azazar can you share the exact dev container configuration (or as close to what you can share publicly), as well as the code in the repository (or something representative, or a high-level description including rough file count if you can't share), and your OS? Using a dev container seems like the best chance to reproduce this
I'm not using dev containers generally. But it crashed again when I checked it in a default debian container. The host used in that test doesn't have AVX2.
I've also installed Ubuntu into QEMU VM (using KVM accelerator) and latest VSCode. Extenstion host got crashed too.
I have avx2
on the Docker server where my code-server container is running, and I have the same problem. So I am unsure that this is the root cause.
so is there a fix for this?
so is there a fix for this?
I wasn't able to find any. qemu-user-static didn't work. Intel SDE didn't work either.
so is there a fix for this?
The fix is to just use Zed (https://zed.dev). It's free, open source, works well and doesn't crash. It has smart integrations with Antropic, OpenAI and Ollama models.
I've been using it and recommend it.
The issue has returned with v0.8.24. Downgrading to v0.8.23 still works.
Working perfectly on v0.8.23-vscode. Later are not.
I'm also facing the same issue when using a machine with a CPU that doesn't have avx2
and fma
.
According to this https://github.com/lancedb/lance/issues/2195#issuecomment-2057841311, one quick way to run lancedb on old CPU is building it from the source by removing the rustflags. 💀
As a workaround, we can build @lancedb/vectordb-linux-x64-gnu
from the source and replace the corresponding file in the Continue
VS Code extension with our compiled version. 💀
I have tested it on my Ivy Bridge CPU, and it works.
Steps:
git clone https://github.com/lancedb/lancedb.git --branch=v0.12.0
# [target.x86_64-unknown-linux-gnu]
# rustflags = ["-C", "target-cpu=haswell", "-C", "target-feature=+avx2,+fma,+f16c"]
node
directory
cd lancedb/node
vectordb
npm install
npm run build-release
Wait for the build to finish. A file named index.node
will be created.
index.node
file in the VS Code extensions directory
cp index.node ~/.vscode/extensions/continue.continue-0.8.55-linux-x64/out/node_modules/@lancedb/vectordb-linux-x64-gnu/index.node
Note that you may need to repeat this workaround (replace the index.node
file) after updating the Continue
extension.
@hahnavi Does this affect builds with avx2?
The issue has returned with v0.8.24. Downgrading to v0.8.23 still works.
Working perfectly on v0.8.23-vscode. Later are not.
confirmed
Debian 11 have same issue, work with v0.8.23-vscode
0.8.44 its working for me!
Hey all, it sounds like https://github.com/continuedev/continue/issues/940#issuecomment-2365339757 is in fact the cause, and that means that https://github.com/continuedev/continue/issues/940#issuecomment-2453564890 is the current workaround.
For a significantly less involved workaround, you can set "disableIndexing": true
in your config.json or .continuerc.json
Because we are unlikely to build separate lancedb binaries ourselves for too many platforms beyond the 6 we already support, I think that the solution is going to either come from LanceDB OR from us eventually supporting swappable vector databases (which is valuable mostly because it would allow VS Code web users to use Continue). This topic had some conversation from a contributor in the last couple weeks, but otherwise isn't planned in the near-term. If anyone is interested in that, please let me know
Type: Bug
Extension host terminated unexpectedly 3 times within the last 5 minutes. Extension bisect identified extension "Continue.continue" as it's cause.
Extension version: 0.8.14 VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:42:16.599Z) OS version: Linux x64 6.1.0-18-amd64 Modes:
System Info
|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz (12 x 3800)| |GPU Status|2d_canvas: enabledcanvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|2, 2, 2| |Memory (System)|23.41GB (10.64GB free)| |Process Argv|. --crash-reporter-id 3667df1a-7faf-4b7a-afa4-cedaa25cb5a4| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|lightdm-xsession| |XDG_CURRENT_DESKTOP|XFCE| |XDG_SESSION_DESKTOP|lightdm-xsession| |XDG_SESSION_TYPE|x11|
A/B Experiments
``` vsliv368:30146709 vspor879:30202332 vspor708:30202333 vspor363:30204092 vstes627:30244334 vscod805cf:30301675 binariesv615:30325510 vsaa593:30376534 py29gd2263:30899288 c4g48928:30535728 azure-dev_surveyone:30548225 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 welcomedialogc:30910334 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 pythontestfixt:30902429 pythonregdiag2:30936856 pyreplss1:30897532 pythonmypyd1:30879173 pythoncet0:30885854 h48ei257:30968133 pythontbext0:30879054 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfcontrol:30979541 8082a590:30971561 a89i1917:30973842 bg6jg535:30979843 dsvsc020:30976470 ```Main Log
Extension Host Log
CON-264