Updated cache-invalidation-api to @33.

chrome/browser/sync/notifier/invalidation_util.cc

Index: chrome/browser/sync/notifier/invalidation_util.cc
diff --git a/chrome/browser/sync/notifier/invalidation_util.cc b/chrome/browser/sync/notifier/invalidation_util.cc
index f61a0db5727ed90fc23ddaaaf6b223251fdd4a0c..a5bc60a65d44f811f30bd3608ef233101a910ff1 100644
--- a/chrome/browser/sync/notifier/invalidation_util.cc
+++ b/chrome/browser/sync/notifier/invalidation_util.cc
@@ -61,9 +61,9 @@ std::string InvalidationToString(
   ss << "components: { ";
   const invalidation::ComponentStampLog& component_stamp_log =
       invalidation.component_stamp_log();
-  for (int i = 0; i < component_stamp_log.stamps_size(); ++i) {
+  for (int i = 0; i < component_stamp_log.stamp_size(); ++i) {

[ghc, 2010/07/09 21:59:40]

It's probably not necessary to print these out at all...  The component stamp
log is really intended for internal monitoring, as it just indicates when the
invalidation flowed through various server-side components.

     const invalidation::ComponentStamp& component_stamp =
-        component_stamp_log.stamps(i);
+        component_stamp_log.stamp(i);
     ss << "component: " << component_stamp.component() << ", ";
     ss << "time: " << component_stamp.time() << ", ";
   }