fix: construct full path for workspaceLogPath instead of just filename

[blink-so]

Problem

The VS Code extension was failing to open SSH proxy log files with the error:

cannot open file:///coder-ssh-20250716-123428-qvict-90716.log. Detail: Unable to read file '/coder-ssh-20250716-123428-qvict-90716.log' (Error: Unable to resolve nonexistent file '/coder-ssh-20250716-123428-qvict-90716.log')

This occurred because workspaceLogPath was being set to just the filename instead of the full path, causing VS Code to look for the file in the wrong location.

Solution

Modified the code in src/remote.ts to properly construct the full path using path.join(logDir, logFileName) instead of just storing the filename.

Before:

this.commands.workspaceLogPath = logFiles
    .reverse()
    .find((file) => file === `${pid}.log` || file.endsWith(`-${pid}.log`));

After:

const logFileName = logFiles
    .reverse()
    .find((file) => file === `${pid}.log` || file.endsWith(`-${pid}.log`));
this.commands.workspaceLogPath = logFileName
    ? path.join(logDir, logFileName)
    : undefined;

Testing

• ✅ TypeScript compilation passes
• ✅ ESLint passes with no style issues
• ✅ Verified the fix constructs proper full paths like /tmp/coder-logs/coder-ssh-20250716-123428-qvict-90716.log

This fix ensures that when users configure the coder.proxyLogDirectory setting and use the "View Logs" command, VS Code can successfully open the SSH proxy log files.

[code-asher]

Good catch, seems we accidentally lost the original path.join() when switching to coder ssh.