[USS] DeviceInfoService's |has_provider_initialized_| is fundamentally broken. |
|||
Issue descriptionRight now, DeviceInfoService subscribes to LocalDeviceInfoProvider's RegisterOnInitializedCallback, and when it gets called, sets a boolean has_provider_initialized_. However, this doesn't really work because the provider will stop giving real data is the user logs out of sync. See https://cs.chromium.org/chromium/src/components/browser_sync/profile_sync_service.cc?q=profile_sync_service.cc&sq=package:chromium&dr&l=773 We need to figure out a way to deal with having local validity of the service fluctuate, and having many entry points from the processor. At very least, has_provider_initialized_ and all the DCHECKs need to be replaced by something.
,
Oct 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fc8171bfb29731cb8f3c302594eb2b9ba9b9239d commit fc8171bfb29731cb8f3c302594eb2b9ba9b9239d Author: skym <skym@chromium.org> Date: Fri Oct 28 22:38:29 2016 [Sync] DeviceInfoService static method and error cleanup. * Exampling upon ModelTypeService's comments to explain when OnMetadataLoaded should be called. * Removed old TODOs from DeviceInfoService * Updated error handling to be slightly more consistent. * Moving static methods to be anonymous namespaced. * Updated unittests to not need static DeviceInfoService methods by modifying the way test data is created. BUG= 659263 Review-Url: https://codereview.chromium.org/2461723002 Cr-Commit-Position: refs/heads/master@{#428527} [modify] https://crrev.com/fc8171bfb29731cb8f3c302594eb2b9ba9b9239d/components/sync/device_info/device_info_service.cc [modify] https://crrev.com/fc8171bfb29731cb8f3c302594eb2b9ba9b9239d/components/sync/device_info/device_info_service.h [modify] https://crrev.com/fc8171bfb29731cb8f3c302594eb2b9ba9b9239d/components/sync/device_info/device_info_service_unittest.cc [modify] https://crrev.com/fc8171bfb29731cb8f3c302594eb2b9ba9b9239d/components/sync/model/model_type_sync_bridge.h
,
Dec 8 2016
,
Jan 17 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by s...@chromium.org
, Oct 25 2016