We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to Reproduce:
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.
The text was updated successfully, but these errors were encountered:
connor4312
No branches or pull requests
Steps to Reproduce:
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:
Selecting the same account to proceed resulted in the following error:
It seems the recent entry is with the URI "vscode://tunnel+xxxx/yyyy" which cause it to resolve tunnel with lower-cased tag.
The text was updated successfully, but these errors were encountered: