Kyle Carberry
Kyle Carberry
@spikecurtis we could check directly for the `sql: database is closed` error, but I'm weary to do so as the error isn't exported in the stdlib sql package.
Great idea. We've had similar thoughts here, it'd be cool to add.
These are tested: https://github.com/coder/coder/blob/f14927955d7361d9a50c633e69fbebca2d9946cb/provisionersdk/agent_test.go#L31
Well, it's not for Windows at the moment, so this issue could be renamed. It tests the fetch and execution of the binary.
Odd. Can you run the "Coder: Show Logs" command?
Hmm, could you paste your SSH config file?
Can you try adding additional `\` to the `ProxyCommand` in the `START CODER VSCODE` section?
Nah, I mean: ``` ProxyCommand "c:\\Users\\samar.elsayed\\AppData\\Roaming\\Code\\User\\globalStorage\\coder.coder-remote\\bin\\coder-windows-amd64.exe" vscodessh --network-info-dir "c:\\Users\\samar.elsayed\\AppData\\Roaming\\Code\\User\\globalStorage\\coder.coder-remote\\net" --log-dir "c:\\Users\\samar.elsayed\\AppData\\Roaming\\Code\\User\\globalStorage\\coder.coder-remote\\log" --session-token-file "c:\\Users\\samar.elsayed\\AppData\\Roaming\\Code\\User\\globalStorage\\coder.coder-remote\\session_token" --url-file "c:\\Users\\samar.elsayed\\AppData\\Roaming\\Code\\User\\globalStorage\\coder.coder-remote\\url" %h ```
What isn't working? I believe our extension works with Cursor.
It should!