Trouble connecting to workspace in VSCode when name matched deleted workspace

[bcpeinhardt]

FYI, we had a report of someone having trouble connecting to a workspace via VS Code when the name matched the name of a previous workspace they had deleted. It seems like there's some state leakage in the VS Code extension.

^ Context linked from Slack.

[gtaylor]

I may be running into the same issue. Here's what I'm seeing

The interesting thing is that I frequently delete and recreate workspaces with the same name but am only just seeing this out of the blue. Looking through my VS Code extensions outputs, the only potentially interesting thing I saw was the Extension Host (local) output:

2025-04-02 10:58:46.797 [error] ProxyResolver#resolveProxy undefined Canceled: Canceled
	at new dR (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:111670)
	at qy.U (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:116281)
	at s.<computed>.n.charCodeAt.s.<computed> (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:113775)
	at cw.resolveProxy (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:109:54839)
	at Object.resolveProxy (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:174:18017)
	at useProxySettings (/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/proxy-agent/out/index.js:182:16)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/proxy-agent/out/index.js:119:13
	at /Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/proxy-agent/out/index.js:707:13
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 
2025-04-02 10:58:46.799 [info] Extension host with pid 21200 exiting with code 0

The Coder output didn't have anything out of the ordinary in it.