-
Notifications
You must be signed in to change notification settings - Fork 480
[release/8.0.1xx] Runtime90357 6012 #6894
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
Conversation
carlossanlop
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving. I am going to assume we will need M2 approval as with any other 8.0 backports if this is merged before the snap.
@jeffhandley does this PR have your approval?
@buyaa-n once merged (if approved) we also need to confirm the change flows into the 8.0 branches of the subscribed repos: sdk, runtime and dotnet-monitor.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release/8.0.1xx #6894 +/- ##
================================================
Coverage 96.39% 96.39%
================================================
Files 1403 1403
Lines 330977 331069 +92
Branches 10890 10894 +4
================================================
+ Hits 319057 319146 +89
- Misses 9187 9190 +3
Partials 2733 2733 |
jeffhandley
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this has my approval. Thanks, @carlossanlop, @buyaa-n, and @manfred-brands!
Backport of #6885 to release/8.0.1xx
/cc @buyaa-n @manfred-brands
Customer Impact
Because of the bug
CA2241: Provide correct arguments to formatting methodsanalyzer throws IndexOutOfRangeException at runtime which causing a build failure in runtime repo and possibly cause same issue for repos that warns as error forAD0001Testing
Unit testing added with the fix, manual testing done with runtime repo
Risk
Low: The fix would cause new warning for an edge case scenario but as the analyzer is at
infolevel by default that is acceptable