Add ongoing events to net-export log when logging starts

components/cronet/android/cronet_url_request_context_adapter.cc

Index: components/cronet/android/cronet_url_request_context_adapter.cc
diff --git a/components/cronet/android/cronet_url_request_context_adapter.cc b/components/cronet/android/cronet_url_request_context_adapter.cc
index 7d0bf0f5f2e7eb86a411b0f72bcf07c3f524077e..a74342c49927392d7455a943f153c02c9a3564cb 100644
--- a/components/cronet/android/cronet_url_request_context_adapter.cc
+++ b/components/cronet/android/cronet_url_request_context_adapter.cc
@@ -10,6 +10,7 @@
 
 #include <limits>
 #include <map>
+#include <set>

[xunjieli, 2017/02/24 18:49:03]

why is this needed?

[wangyix1, 2017/02/24 22:07:19]

The first param to CreateNetLogEntriesForActiveObjects() at line 1030 is const
std::set<URLRequestContext*>& contexts; I just used an initializer list for that
param.

[xunjieli, 2017/02/24 22:10:08]

Acknowledged.

[eroman, 2017/02/24 23:43:45]

I don't think you quite answered Helen's question.

cronet_url_request_context_adapter.cc was already including <set> transitively
by way of "net/log/net_log_util.h".

So in that sense, the addition of <set> should not have been needed for
compilation sake (if you remove the line it still compiles right?). In general
APIs that take a std::set<> will end up polluting <set> since it can't be
forward declared.

Including <set> in this file explicitly isn't necessarily a bad thing. Adherents
of the include-what-you-use would encourage doing so.

However we don't enforce IWYU in Chrome thanks to lack of tooling support, so I
would say this include is entirely optional, and Helen's question still stands.

I don't really care whether we include <set> here or not. But would like to see
the motivation explained one way or another.

Thanks!

 #include <utility>
 #include <vector>
 
@@ -1022,16 +1023,18 @@ void CronetURLRequestContextAdapter::StartNetLogToBoundedFileOnNetworkThread(
   base::FilePath file_path(dir_path);
   DCHECK(base::PathIsWritable(file_path));
 
-  bounded_file_observer_.reset(
-      new net::FileNetLogObserver(GetFileThread()->task_runner()));
+  bounded_file_observer_ = net::FileNetLogObserver::CreateBounded(
+      GetFileThread()->task_runner(), file_path, size, kNumNetLogEventFiles,
+      /*constants=*/nullptr);
+
+  CreateNetLogEntriesForActiveObjects({context_.get()},
+                                      bounded_file_observer_.get());
 
   net::NetLogCaptureMode capture_mode =
       include_socket_bytes ? net::NetLogCaptureMode::IncludeSocketBytes()
                            : net::NetLogCaptureMode::Default();
-
-  bounded_file_observer_->StartObservingBounded(
-      g_net_log.Get().net_log(), capture_mode, file_path,
-      /*constants=*/nullptr, context_.get(), size, kNumNetLogEventFiles);
+  bounded_file_observer_->StartObserving(g_net_log.Get().net_log(),
+                                         capture_mode);
 }
 
 void CronetURLRequestContextAdapter::StopBoundedFileNetLogOnNetworkThread() {