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

[release/8.0.2xx] fix(CA2208): false positive when message start with parameter name followed by punctuation #7092

Merged
merged 1 commit into from
Dec 14, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 12, 2023

Backport of #7065 to release/8.0.2xx

/cc @buyaa-n @HenryZhang-ZHY

Customer Impact

Several customers reported this regression: #6863, #6925, #7056. The enhancement we made in 8.0 Relax name validation in CA2208 had a side effect that caused the regression that introduces new false positive diagnostics for the case mentioned in the issue. In case user set warn as error for the CA2208 the new diagnostics could break the build.

Testing

A unit test that reproduces the issue is added with the PR

Risk

Very low, the fix is clear and straight forward, don't expect it cause any bad side effect.

@github-actions github-actions bot requested a review from a team as a code owner December 12, 2023 17:38
Copy link

codecov bot commented Dec 12, 2023

Codecov Report

Merging #7092 (93e7073) into release/8.0.2xx (7e5f473) will decrease coverage by 0.01%.
The diff coverage is 97.56%.

Additional details and impacted files
@@                 Coverage Diff                 @@
##           release/8.0.2xx    #7092      +/-   ##
===================================================
- Coverage            96.39%   96.39%   -0.01%     
===================================================
  Files                 1402     1402              
  Lines               332264   332297      +33     
  Branches             11065    11066       +1     
===================================================
+ Hits                320288   320302      +14     
- Misses                9204     9220      +16     
- Partials              2772     2775       +3     

@buyaa-n buyaa-n added the servicing-consider For backport requests to servicing branches. label Dec 12, 2023
@carlossanlop carlossanlop added servicing-approved and removed servicing-consider For backport requests to servicing branches. labels Dec 14, 2023
@carlossanlop
Copy link
Member

Approved by Tactics in today's meeting.

@carlossanlop
Copy link
Member

Please don't merge yet. I need some clarity on whether we're ok in continuing merging backports to the old 8.0.2xx branch, or if we have to wait for 8.0.3xx to be snapped and then retarget this PR to that branch.

@carlossanlop
Copy link
Member

Ok got clarity. The 8.0.2xx branch is still open for changes until Jan 5th. We can get this merged and we can flow it via darc to the sdk.

@carlossanlop carlossanlop added this to the 8.0.2xx milestone Dec 14, 2023
@carlossanlop carlossanlop merged commit abef8ce into release/8.0.2xx Dec 14, 2023
11 checks passed
@carlossanlop carlossanlop deleted the backport/pr-7065-to-release/8.0.2xx branch December 14, 2023 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants