Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.0a19
2023.1.0a3
Issue ID
UUM-9085
Regression
No
[Roslyn Analyzers] Warning messages do not stay after compilation is complete when a ruleset file is modified
Reproduction steps:
1. Open the user's attached project
2. Open Assets/Scripts/Default.ruleset
3. In Visual Studio expand Microsoft.Unity.Analyzers
4. Modify a rule action (e.g. change rule UNT0020 from "Warning" to "None")
5. Save and go back to Unity Editor
6. Observe the Console window
Expected result: Warning messages stay when the compilation is complete
Actual result: Warning messages appear for a short time and then disappear when the compilation is complete
Reproducible with: 2022.2.0b1, 2023.1.0a3
Not reproducible with: 2019.4.40f1, 2020.3.35f1, 2021.3.5f1, 2022.1.8f1, 2022.2.0a19
Reproducible on: Windows 10
Notes:
1. Modifying a c# script file and compiling results in a correct behavior
2. Look at the attached video for clarity
Warning messages:
warning UNT0001: The Unity message 'Start' is empty.
warning UNT0001: The Unity message 'Update' is empty.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Render Graph Viewer Capture button plays the click animation but does not do anything when the Capture button is pressed with the “Enter” key on the keyboard
- UI Builder Scrollview is unable to scroll all the way down when the window is downsized vertically
- Celestial bodies order remains unchanged when the Distance setting is modified
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
Resolution Note:
The repro project includes a `OnPostprocessAllAssets` - that calls CompilationPipeline.RequestScriptCompilation();
That will trigger a recompilation of things that has changed, and clears logs from the last compilation.