Send important client side event information to the server.

chrome/browser/sync/protocol/client_debug_info.proto

+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+//
+// Common sync protocol for encrypted data.
+
+// Update proto_value_conversions{.h,.cc,_unittest.cc} if you change
+// any fields in this file.
+
+syntax = "proto2";
+
+option optimize_for = LITE_RUNTIME;
+option retain_unknown_fields = true;
+
+package sync_pb;
+
+message SyncCycleCompletedEventInfo {
+  optional bool syncer_stuck = 1;
+  optional int32 num_blocking_conflicts = 2;
+  optional int32 num_non_blocking_conflicts = 3;
+}
+
+message DebugEventInfo {
+  // these events dont have any extra info associated with them.

[tim (not reviewing), 2011/10/13 16:04:14]

Comments should start with a capital.

[lipalani1, 2011/10/13 21:39:18]

Done.

+  enum EventType {
+    AUTH_ERROR = 1; // Auth error
+    UPDATED_TOKEN = 2; // Client received an updated token.
+    PASSPHRASE_REQUIRED = 3; // Cryptographer needs passphrase.
+    PASSPHRASE_ACCEPTED = 4; // Passphrase was accepted by cryptographer.
+    INITIALIZATION_COMPLETE = 5; // Sync Initialization is complete.
+    // This event should never be seen by the server in the absence of bugs.
+    STOP_SYNCING_PERMANENTLY = 6; // Server sent stop syncing permanently.
+    ENCRYPTION_COMPLETE = 7; // Client has finished encrypting all data.
+    ACTIONABLE_ERROR = 8; // Client received an actionable error.
+  }
+  optional EventType type = 1;
+  optional SyncCycleCompletedEventInfo sync_cycle_completed_event_info = 2;
+}
+
+message DebugInfo {

[tim (not reviewing), 2011/10/13 16:04:14]

We had discussed time deltas for events.  I still think that's useful. 

We're populating |events| using the queue, right?  Do we want a bit tracking
whether we overwrote data?

[lipalani1, 2011/10/13 21:39:18]

TimeDeltas need some thinking through to send in a bandwidth optimized way. And
I would be happy to consider it as the next evolution of this feature. Added a
bit to track if events were dropped. Good idea!
On 2011/10/13 16:04:14, timsteele wrote:

+  repeated DebugEventInfo events = 1;
+  optional bool cryptographer_ready = 2;
+  optional bool cryptographer_has_pending_keys = 3;
+}