-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Logging: code-insiders --log
did not work for me.
#164661
Comments
|
can you please try |
|
|
@deepak1556 Your expertise is needed here. How can we know why code insiders is not launching with following command |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
We can first check if the cli script didn't encounter any exception and ended up calling into the main application, the signal for this would be to see if child_process.spawn call got triggered. @karthiknadig can you try the following, and copy any logs printed to the terminal after
|
This is what I got:
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
@deepak1556 @sandy081 This seems to be closed automatically. I have provided the re-quested logs. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
CC @deepak1556 |
@deepak1556 Can you please check this comment |
Side-effect of #188769, this should be addressed with latest insiders. |
Testing #164434
This command did not work for me
code-insiders --log vscode.git:trace .
butcode-insiders .
works. I verified thatvscode.git
is installed.Version: 1.73.0-insider (system setup)
Commit: a803dc3
Date: 2022-10-25T05:18:55.889Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: Yes
The text was updated successfully, but these errors were encountered: