Fix strong_memoize in UpdateRemoteMirrorService and UpdateMirrorService
The following discussion from !148368 (merged) should be addressed:
-
@mbobin started a discussion: (+3 comments) I think this is a bug waiting to happen because using
strong_memoize
on a method that accepts arguments caches and returns the same result for subsequent calls regardless of the argument given.😬 I see that we call this once, so there should not be any reason to memoize the result.