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
When trying to add a trino connection I'm getting the following error: Unable to write file '/.vscode/settings.json' (Unknown (FileSystemError): Error: EROFS: read-only file system, mkdir '/.vscode')
To Reproduce
Steps to reproduce the behavior:
Go to SQL Tools extension on sidebar
Click on Add Connection
Fill in connection settings
Click on save connection
Expected behavior
Connection should be saved with details registered into settings.json
Screenshots
Desktop (please complete the following information):
SQLTools Version v0.28.1
VS Code Version: 1.84.2
OS: MacOS Sonoma
Driver:
Trino
Additional context
If I insert all details manually I'm able to see the database, but not sure if I'm getting the manual setup correctly because I can't seem to connect (although when utilizing the UI and clicking on Test Connection it does work - but cannot save)
The text was updated successfully, but these errors were encountered:
Hello @gjsjohnmurray i believe I can, but I'm not sure how to do it, are you able to give me some tips on where I'd be able to do it? I'm kinda new to VSCode coming from R
Describe the bug
When trying to add a trino connection I'm getting the following error:
Unable to write file '/.vscode/settings.json' (Unknown (FileSystemError): Error: EROFS: read-only file system, mkdir '/.vscode')
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connection should be saved with details registered into settings.json
Screenshots
Desktop (please complete the following information):
Additional context
If I insert all details manually I'm able to see the database, but not sure if I'm getting the manual setup correctly because I can't seem to connect (although when utilizing the UI and clicking on Test Connection it does work - but cannot save)
The text was updated successfully, but these errors were encountered: