Reland: S13n: Add APIs for implementing net-export in Network Service
Change for reland: The debug bot failure was because tests passed an invalid base::File to a method with a mojo_base.mojom.File --- as opposed to mojo_base.mojom.File? --- parameter type. This commits to not accepting those files, by adding an additional DCHECK on it and adjusting tests to not do that. Rationale: passing in a broken file is ultimately doing an RPC to do a lot of work that accomplishes nothing, so it's silly to support it, even if a 1-character fix CL would be easier. Original CL: https://chromium-review.googlesource.com/c/chromium/src/+/1030033 Original description: S13n: Add APIs for implementing net-export in Network Service (But don't use them yet). This takes care of managing the FileNetLogObserver with a passed-in destination file, and also of all aspects of pulling state from URLRequestContexts, which browser-end NetExportFileExporter presently does but won't be able to with network service. There is one behavior difference in that respect: the in-progress entries for things that are in flight when the export is started now included all URLRequestContexts known, rather than just the main + media + system for whever the export UI is running. Given that events collected when export is active included everything already, this seemed rational as consistent, and avoiding complexity of finding the particular contexts, including the going-away media one. Bug: 767450 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo Change-Id: Ifd7f8fbcd60ec2dadf7a8b31c6b0ec67d27b9b7b Reviewed-on: https://chromium-review.googlesource.com/1037243 Commit-Queue: Maks Orlovich <morlovich@chromium.org> Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
Helen Li <xunjieli@chromium.org> Cr-Commit-Position: refs/heads/master@{#555870}
Showing
Please register or sign in to comment