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
Please DO NOT add debug env so that the vscode remote server will be effected by this.
And user's dev progress will output so many useless logs.
For example, when I installed SQLTools in remote server, and start a Node.js debug progress via npm run dev, the terminal outputs so many installed dependencies debug logs which are unexpected and noisy.
To Reproduce
Steps to reproduce the behavior:
Install Remote - SSH ext and open a remote project
Open a new terminal window after SQLTools activated
Output the process.env.DEBUG in Node.js or run echo $DEBUG
It outputs *,-*:debug,-*:*:debug,-*:*:*:debug,-*:*:*:*:debug,-*:*:*:*:*:debug or *,-babel*,-*:debug,-*:*:debug,-*:*:*:debug,-*:*:*:*:debug,-*:*:*:*:*:debug
Expected behavior
No debug env added.
Screenshots
Desktop (please complete the following information):
SQLTools Version 0.22.10
VSCode Version: 1.46.1
OS: macOS 10.15.5 (local) and Ubuntu 18.04 (remote)
Driver:
PostgreSQL/Redshift
MySQL/MariaDB
MSSQL/Azure
SQLite
Other? Which...
Database version: [e.g. MySQL v5.6, PostgreSQL vX...]
Describe the bug
Please DO NOT add debug env so that the vscode remote server will be effected by this.
And user's dev progress will output so many useless logs.
For example, when I installed SQLTools in remote server, and start a Node.js debug progress via
npm run dev
, the terminal outputs so many installed dependencies debug logs which are unexpected and noisy.To Reproduce
Steps to reproduce the behavior:
Remote - SSH
ext and open a remote projectecho $DEBUG
*,-*:debug,-*:*:debug,-*:*:*:debug,-*:*:*:*:debug,-*:*:*:*:*:debug
or*,-babel*,-*:debug,-*:*:debug,-*:*:*:debug,-*:*:*:*:debug,-*:*:*:*:*:debug
Expected behavior
No debug env added.
Screenshots
Desktop (please complete the following information):
Additional context
Related issue: microsoft/vscode-remote-release#3091
The text was updated successfully, but these errors were encountered: