molstar/VSCoding-Sequence

Error: Could not register service worker , when Launch from Folder

linonetwo opened this issue · 2 comments

Error: Could not register service worker: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state..

图片

Log from extension host:

2024-05-08 23:10:00.426 [error] TypeError: Cannot read properties of undefined (reading 'dispose')
    at a.dispose [as value] (c:\Users\linonetwo\.vscode\extensions\arianjamasb.protein-viewer-0.1.0\src\panels\ProteinViewerPanel.ts:49:17)
    at o.y (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:82:660)
    at o.fire (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:82:877)
    at A.dispose (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:155:48761)
    at P.$onDidDisposeWebviewPanel (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:155:50797)
    at c.S (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:5505)
    at c.Q (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:5271)
    at c.M (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:4361)
    at c.L (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:3440)
    at a.value (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:2227)
    at o.y (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:82:660)
    at o.fire (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:82:877)
    at u.fire (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:107:14175)
    at a.value (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:176:8023)
    at o.y (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:82:660)
    at o.fire (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:82:877)
    at u.fire (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:107:14175)
    at MessagePortMain.<anonymous> (c:\Users\linonetwo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:176:6303)
    at MessagePortMain.emit (node:events:517:28)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2285)

Hi @linonetwo, would you be able to share the trajectory files so I can try to diagnose this?

Thanks for response, strangely, it works this time, maybe restart PC fix the "state"?

The pdb are example output of https://github.com/RosettaCommons/RFdiffusion , shoudn't have anything wrong.
test_outputs.zip