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

skip scanning for a user when the user is not setup yet #25028

Merged
merged 1 commit into from Jun 9, 2016

Conversation

icewind1991
Copy link
Contributor

Otherwise an invalid 'home storage not writable' error is thrown

cc @owncloud/filesystem

@icewind1991 icewind1991 added this to the 9.1-current milestone Jun 8, 2016
@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @DeepDiver1975, @MorrisJobke and @oparoz to be potential reviewers

@PVince81
Copy link
Contributor

PVince81 commented Jun 8, 2016

Tested, works 👍

Note: before this fix the scanner did properly continue even after the error message, so this fix isn't that critical.

@mmattel second review ?

@mmattel
Copy link
Contributor

mmattel commented Jun 8, 2016

Tested and works 👍
(if merged, backporting?)

@PVince81
Copy link
Contributor

PVince81 commented Jun 8, 2016

Okay, a backport here doesn't hurt

CC @dragotin @DeepDiver1975

@icewind1991 please backport to 9.0

@PVince81
Copy link
Contributor

PVince81 commented Jun 8, 2016

note: only affects the CLI scanner. it's not the internal scanner.

@PVince81 PVince81 merged commit 0e3737f into master Jun 9, 2016
@PVince81 PVince81 deleted the scanner-user-not-setup branch June 9, 2016 08:29
@mmattel
Copy link
Contributor

mmattel commented Jun 9, 2016

@PVince81 shall we close #25020 or leave it open for the other referenced issues?

@PVince81
Copy link
Contributor

PVince81 commented Jun 9, 2016

I'll close it. The referenced issues are enough and stand by themselves.

@PVince81
Copy link
Contributor

PVince81 commented Jun 9, 2016

stable9: #25044

@lock
Copy link

lock bot commented Aug 5, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants