Track merged nudge sources

sync/protocol/client_debug_info.proto

Index: sync/protocol/client_debug_info.proto
diff --git a/sync/protocol/client_debug_info.proto b/sync/protocol/client_debug_info.proto
index 7e4e1a5f961f1d57b5808f35cecdd2af02f0da6b..61ef9b220b4ecd2f2f93c849030ee50458a01bb2 100644
--- a/sync/protocol/client_debug_info.proto
+++ b/sync/protocol/client_debug_info.proto
@@ -13,6 +13,18 @@ package sync_pb;
 
 import "get_updates_caller_info.proto";
 
+// Information about hints sent with nudges.
+message TypeHint {
+  optional int32 data_type_id = 1;
+  optional bool has_valid_hint = 2;
+}
+
+// Information about the source that triggered a sync.
+message SourceInfo {
+  optional GetUpdatesCallerInfo.GetUpdatesSource source = 1;
+  repeated TypeHint type_hint = 2;
+}
+
 // The additional info here is from the StatusController. They get sent when
 // the event SYNC_CYCLE_COMPLETED  is sent.
 message SyncCycleCompletedEventInfo {
@@ -38,6 +50,8 @@ message SyncCycleCompletedEventInfo {
   optional int32 num_updates_downloaded = 8;
   optional int32 num_reflected_updates_downloaded = 9;
   optional GetUpdatesCallerInfo caller_info = 10;
+
+  repeated SourceInfo source_info = 11;

[tim (not reviewing), 2012/11/29 19:28:05]

sources_list may be a better name (to match debug_info_sources_list more
closely).  A comment explaining how this gets populated would be good too.  You
might consider giving a heads up to someone using this to debug that no efforts
are made to avoid spurious / duplicate back-to-back entries in this list,  (as
canary jobs and mode switches (client side) will cause this, for the moment).   

[rlarocque, 2012/11/29 23:42:12]

I thought of that, but then there's the problem that the protobuf generated
function names don't make sense.  I think add_source_info() is a more accurate
function name than add_sources_list(), so that's why I kept the field name
singular.
Good point.  Will fix.

 }
 
 // Datatype specifics statistics gathered at association time.