Chromium Code Reviews| Index: sync/engine/non_blocking_type_commit_contribution.cc |
| diff --git a/sync/engine/non_blocking_type_commit_contribution.cc b/sync/engine/non_blocking_type_commit_contribution.cc |
| index 5216ed08add0e47d47558407b0101052a77da773..d4506b33e3b5dfc8829184eeed45f22d1dc27388 100644 |
| --- a/sync/engine/non_blocking_type_commit_contribution.cc |
| +++ b/sync/engine/non_blocking_type_commit_contribution.cc |
| @@ -62,13 +62,13 @@ syncer::SyncerError NonBlockingTypeCommitContribution::ProcessCommitResponse( |
| case sync_pb::CommitResponse::INVALID_MESSAGE: |
| LOG(ERROR) << "Server reports commit message is invalid."; |
| DLOG(ERROR) << "Message was: " |
| - << syncer::SyncEntityToValue(entities_.Get(i), false); |
| + << syncer::SyncEntityToValue(entities_.Get(i), false).get(); |
|
dcheng
2016/01/19 23:50:55
This seems pretty silly: we log out a pointer valu
|
| unknown_error = true; |
| break; |
| case sync_pb::CommitResponse::CONFLICT: |
| DVLOG(1) << "Server reports conflict for commit message."; |
| DVLOG(1) << "Message was: " |
| - << syncer::SyncEntityToValue(entities_.Get(i), false); |
| + << syncer::SyncEntityToValue(entities_.Get(i), false).get(); |
| commit_conflict = true; |
| break; |
| case sync_pb::CommitResponse::SUCCESS: { |