Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to open recent remote folder/workspace when tunnel is tagged with uppercase character #9700

Open
takerusilt opened this issue Mar 26, 2024 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug tunnels

Comments

@takerusilt
Copy link

  • Extension version: v1.6.2024032609
  • VSCode Version: 1.87.2
  • Local OS Version: macOS 13.6.3 / 14.0
  • Remote OS Version:
  • Remote Extension/Connection Type: Server

Steps to Reproduce:

  1. On remote computer, turn on Remote Tunnel Access. A tunnel is created with tag in uppercase character, e.g. "XXXX"
  2. On local computer, connect tunnel "XXXX", open arbitrary file/folder/workspace on remote computer
  3. Close remote connection
  4. Trigger "File: Open Recent..."
  5. Select "yyyyy [XXXX]" entry (which is created by step 2)

Expected:

Able to resolve tunnel XXXX and open remote file/folder/workspace (given that current session is already logged in having access to tunnel XXXX)

Result:

Prompted for login, where output terminal for "Remote - Tunnels" shows:

2024-03-26 18:03:03.192 [info] Resolving tunnel+xxxx...
2024-03-26 18:03:03.210 [info] Creating new tunnel proxy server

Selecting the same account to proceed resulted in the following error:

2024-03-26 18:05:50.523 [error] [proxy] Tunnel with tag xxxx not found

It seems the recent entry is with the URI "vscode://tunnel+xxxx/yyyy" which cause it to resolve tunnel with lower-cased tag.

@aeschli aeschli assigned connor4312 and unassigned aeschli Mar 26, 2024
@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug tunnels labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug tunnels
Projects
None yet
Development

No branches or pull requests

3 participants