-
Notifications
You must be signed in to change notification settings - Fork 2.1k
detect correct uid when even wrong casing in given uid for files:scan #35324
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
|
@karakayasemi yes, I do agree with you. Better getting the right uid instead of throwing an exception. thank you. |
d687e14 to
d4bd6fe
Compare
Codecov Report
@@ Coverage Diff @@
## master #35324 +/- ##
=============================================
- Coverage 65.53% 48.87% -16.67%
=============================================
Files 1218 109 -1109
Lines 70548 10560 -59988
Branches 1288 1288
=============================================
- Hits 46235 5161 -41074
+ Misses 23936 5022 -18914
Partials 377 377
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #35324 +/- ##
============================================
+ Coverage 65.53% 65.53% +<.01%
Complexity 18648 18648
============================================
Files 1218 1218
Lines 70548 70549 +1
Branches 1288 1288
============================================
+ Hits 46235 46236 +1
Misses 23936 23936
Partials 377 377
Continue to review full report at Codecov.
|
|
I added |
|
Backport PR: #35344 |
Description
When doing a files:scan and entering the user id in the wrong case. The job tells, that no files are scanned. This PR fixes issue by learning correct uid from user manager. @pako81 since casing is not important in our uid policy, in my opinion this solution better than throwing an error. Do you think this PR is acceptable with this behavior?
Related Issue
Motivation and Context
Solving bugs.
How Has This Been Tested?
Types of changes
Checklist:
Open tasks: