You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Open VSC SAS Extension base on Main branch. Sign in with a valid Viya connection, open SAS server. Open a .sas file and open Command Palette, find the command 'SAS:Add New Connection Profile' to add a new valid SSH connection. Error happened if trying to connect to the newly created SSH profile.
Steps to reproduce
Sign in with a valid viya connection
Open SAS Server and keep it visible
Open a .sas file
Open Command palette
Find command 'SAS:Add New Connection Profile'
Create a new valid SSH connection profile
Expected behavior
No error if trying to use the newly created SSH connection profile
Screenshots
Environment (please complete the following information):
Client OS: [e.g. Windows 11]
Extension version: [e.g. v1.12.0]
The text was updated successfully, but these errors were encountered:
@Zhirong2022 Just for clarification, users can use ssh connections, right? But, creating a new ssh connection while being connected to a viya 4 connection causes issues. Is that right?
@Zhirong2022 Just for clarification, users can use ssh connections, right? But, creating a new ssh connection while being connected to a viya 4 connection causes issues. Is that right?
@scottdover Yes, it is the scenario. User can use ssh connection as usual.
Describe the bug
Open VSC SAS Extension base on Main branch. Sign in with a valid Viya connection, open SAS server. Open a .sas file and open Command Palette, find the command 'SAS:Add New Connection Profile' to add a new valid SSH connection. Error happened if trying to connect to the newly created SSH profile.
Steps to reproduce
Expected behavior
No error if trying to use the newly created SSH connection profile
Screenshots
Environment (please complete the following information):
Client OS: [e.g. Windows 11]
Extension version: [e.g. v1.12.0]
The text was updated successfully, but these errors were encountered: