Skip to content

Double check for failed cache with a shared storage - #11862

Merged
blizzz merged 1 commit into
masterfrom
bugfix/ensure_cache_it_init
Oct 17, 2018
Merged

Double check for failed cache with a shared storage#11862
blizzz merged 1 commit into
masterfrom
bugfix/ensure_cache_it_init

Conversation

@rullzer

Copy link
Copy Markdown
Member

When obtaining the SourceRootInfo we can call init. If this fails the
cache is set to a failed cache and the storage to a failed storage.
However we did not check for this. Which means that if the storage was
invalid it would fail later on.

Now we will properly error out.

This should fix warnings on our own instance where I could trigger it.

When obtaining the SourceRootInfo we can call init. If this fails the
cache is set to a failed cache and the storage to a failed storage.
However we did not check for this. Which means that if the storage was
invalid it would fail later on.
Now we will properly error out.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
@rullzerrullzer added this to the Nextcloud 15 milestone Oct 16, 2018
@rullzer

Copy link
Copy Markdown
MemberAuthor

I thin we just miss an init somewhere.
Would probably be cleaner to do that.

@rullzer

Copy link
Copy Markdown
MemberAuthor

I vote to get this in. As it is an easily backportable fix.

@blizzz
blizzz merged commit 2634ceb into masterOct 17, 2018
@blizzz
blizzz deleted the bugfix/ensure_cache_it_init branch October 17, 2018 11:13
@MorrisJobke

Copy link
Copy Markdown
Member

@rullzer Mind to open the backport PR?

@rullzer

Copy link
Copy Markdown
MemberAuthor

Not yet. It seems this created a different issue on the account of @nickvergessen. I need to investigate that further.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to reviewWaiting for reviewsbug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rullzer@MorrisJobke@icewind1991@blizzz