New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 661240 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

[USS] Stop forcing model type to use unset SyncErrors

Project Member Reported by s...@chromium.org, Nov 1 2016

Issue description

Right now we have SyncErrors all over ModelTypeChangeProcessor methods and ModelTypeSyncBridge's callbacks. These are pretty much uniformly unused. If the model type has a synchronous implementation, then it likely cannot encounter an error. If it is asynchronous, then the processor has already lost all the context that would allow it to do anything intelligent and retry.

Lets remove SyncErrors from these interfaces, and allow the model type to at any point tell the processor that it's encountered an error. If the processor was waiting for metadata, then it will want to try to send it on through start_callback_.
 
Status: Available (was: Untriaged)

Comment 2 by s...@chromium.org, Mar 10 2017

Status: Fixed (was: Available)

Sign in to add a comment