-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix files scan repair in bulk warning #29629
Conversation
fyi: this has also been recently documented in owncloud-archive/documentation#3545 and doc backported to stable 10 |
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.
Tested and works
Codecov Report
@@ Coverage Diff @@
## master #29629 +/- ##
============================================
- Coverage 61.82% 61.82% -0.01%
Complexity 17501 17501
============================================
Files 1045 1045
Lines 57712 57713 +1
============================================
Hits 35683 35683
- Misses 22029 22030 +1
Continue to review full report at Codecov.
|
I've added some tests to make codecov happy. The occ files:scan command didn't have any tests at all... Please check ba21954 cc @DeepDiver1975 ^ |
pfff, tests pass locally but not on Jenkins. I'll move those to a separate PR |
moved tests here: #29635 |
ba21954
to
6b42f5a
Compare
waiting for drone now... |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
Fix warning when running
occ files:scan --repair --all
without single user mode.The message now only appears when
--repair
is actually passed.Additionally, the message was improved to make more sense when read in this context.
The command now exits with an error code as it doesn't make sense to scan since the precondition was not met.
Related Issue
Found during smoke testing for 9.0.11RC1: #29627
Motivation and Context
How Has This Been Tested?
Manual testing of command with and without single user mode.
Without repair switch, no message must appear.
Screenshots (if appropriate):
Types of changes
Checklist:
Backports: