Skip to content

Add verbose logging to help isolate race conditions in errorlist #51521

@vatsalyaagrawal

Description

@vatsalyaagrawal

Customers have reported that at times diagnostics that stick around, even once customer has fixed them. i.e. even after doing a full (successful) build. This scenario usually happens when customers attempt a series of quick edits/changes/refactorings. Potentially there is a race condition somewhere. This leads to confusion.

At this point we do not have a repro, thus it is very difficult to isolate the issue at hand. We can potentially add additional logging that customers can enable when they hit this issue. Hopefully additional logging will help us address this bug.

Metadata

Metadata

Assignees

Labels

Area-IDEConcept-Design DebtEngineering Debt, Design Debt, or poor product code qualityTenet-TelemetryOur ability to collect telemetry is broken.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions