Latest Capture Pull Request

[jspahn80134]

No description provided.

[bjones1]

I assume you want to run the debugger to check code running inside the VSCode extension, not simply code running in the standalone server?

On a side note, you can run ./bt flint from the server/ directory to clean/lint the code.

[bjones1]

I haven't done that yet -- it's definitely valuable to be able to do, but probably also hard. I typically write unit tests and debug those, since it's less connected to the VSCode environment and problems there.

[bjones1]

I can see several errors at the TypeScript level, just by starting the VSCode debugger on the CodeChat Editor extension for VSCode, starting the extension in the extension debug host, then opening the webview developer tools:

This may mean I'm not running the server and not be real failure indication, not sure.

Here's a launch.json profile that may work:

        {
            "name": "Attach Rust",
            "type": "lldb",
            "request": "attach",
            // Use the VSCode process explorer to find the correct VSCode process.
            "pid": "${command:pickProcess}",
            // Path to the compiled Rust binary/library.
            "program": "${workspaceFolder}/out/codechat-editor-client.win32-x64-msvc.node",
        }