Jupyter Notebooks in VSCode become unresponsive because the kernel gets disposed erroneously about continue HOT 5 OPEN

+1 to this problem, also documented on a vsCode repo issue here microsoft/vscode#214848 (comment), where @BabakAmini also narrowed the issue down to this extension

I am also getting this issue on MacOS Ventura when connecting to a linux server over SSH.

from continue.

Hi,

Same issue here when using from Ubuntu server via SSH.
Disabling indexing is a work around. I hope it helps

Here are my VScode logs :

console.ts:137 [Extension Host] Error updating the sqliteFts index: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: fts_metadata.id C @ console.ts:137 $logExtensionHostMessage @ mainThreadConsole.ts:39 S @ rpcProtocol.ts:458 Q @ rpcProtocol.ts:443 M @ rpcProtocol.ts:373 L @ rpcProtocol.ts:299 (anonymous) @ rpcProtocol.ts:161 y @ event.ts:1196 fire @ event.ts:1227 fire @ ipc.net.ts:650 U.onmessage @ localProcessExtensionHost.ts:378 log.ts:439 ERR unknown text editor: 0a28d7b1-da06-403e-92c8-20004159d542. known editors: : Error: unknown text editor: 0a28d7b1-da06-403e-92c8-20004159d542. known editors: at $.getEditorById (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:160:1516) at R.$acceptEditorPropertiesChanged (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:155:164785) at E.S (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:152:5970) at E.Q (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:152:5736) at E.M (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:152:4762) at E.L (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:152:3589) at n.value (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:152:2282) at l.y (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:82:664) at l.fire (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:82:881) at s.fire (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:107:14502) at n.value (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:178:8481) at l.y (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:82:664) at l.fire (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:82:881) at s.fire (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:107:14502) at h.z (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:107:17638) at n.value (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:107:17012) at l.y (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:82:664) at l.fire (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:82:881) at u.acceptChunk (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:107:12248) at /home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:107:11518 at Socket.w (/home/jgodfroy/.vscode-server/cli/servers/Stable-5437499feb04f7a586f677b155b039bc2b3669eb/server/out/vs/workbench/api/node/extensionHostProcess.js:175:13305) at Socket.emit (node:events:518:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

from continue.

In my case, it was fixed after a couple of days of disabling and then re-enabling the extension. I had assumed that the recent update was the culprit, but now that it is failing, I have to disable it once more.

from continue.

I am having the same issue, can't use Continue with Jupyter in VSCode...

from continue.

Same issue here....

[info] Disposing request as the cell (-1) was deleted

from continue.