Skip to content
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

C/C++.log for writing: Operation timed out #3717

Closed
dnicolson opened this issue May 31, 2019 · 5 comments
Closed

C/C++.log for writing: Operation timed out #3717

dnicolson opened this issue May 31, 2019 · 5 comments
Labels
bug duplicate fixed Check the Milestone for the release in which the fix is or will be available. Visual Studio Code Caused by (or depends on changes from) VS Code

Comments

@dnicolson
Copy link

Type: General

When running npm test there are strange errors caused by the C/C++ extension.

Describe the bug

  • OS and Version: macOS 10.14.5 (18F132)
  • VS Code Version: 1.34.0
  • C/C++ Extension Version: 0.23.1

To Reproduce
Steps to reproduce the behavior:

  1. Run yo code with default options
  2. Run npm test

Expected behavior
The C/C++ extension not to log anything. After the test output the following appears:
Error: Failed opening file [path]/output_logging_20190531T195912/5-C/C++.log for writing: Operation timed out.

Disabling the extension does not prevent the error, the extension must be uninstalled.

@sean-mcmanus
Copy link
Collaborator

This is bug microsoft/vscode#73441 -- fixed with the latest VS Code Insiders.

@sean-mcmanus sean-mcmanus added bug duplicate fixed Check the Milestone for the release in which the fix is or will be available. Visual Studio Code Caused by (or depends on changes from) VS Code labels May 31, 2019
@sean-mcmanus
Copy link
Collaborator

But that error shouldn't repro if the C/C++ extension is disabled (it seems like the disabling might not be working for you?).

@dnicolson
Copy link
Author

It looked unique as the filename and error message is different.

@sean-mcmanus
Copy link
Collaborator

The log in microsoft/vscode#73441 has "Diagnostics" at the end because it's from the C/C++: Log Diagnostics command, but the same root issue occurs for the normal C/C++ output window (log).

@sean-mcmanus
Copy link
Collaborator

sean-mcmanus commented May 31, 2019

The other error message differences might be due to the OS being used (my error is from Windows).

Let us (or the VS Code team) know if the bug still repros with Insiders...it could be another spot in VS Code hitting the same issue with parsing "C/C++" incorrectly.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate fixed Check the Milestone for the release in which the fix is or will be available. Visual Studio Code Caused by (or depends on changes from) VS Code
Projects
None yet
Development

No branches or pull requests

2 participants