GitLab

expand_thin_archives contained logic that was a duplicate of
what's in goma_link.py. This refactoring changes expand_thin_archives
to call into goma_link (or goma_ld) to perform the expansion, and
remove the duplicated code.

With the duplication removed, expand_thin_archives is now Py3
compatible!

Bug: chromium:941669
Change-Id: Ia258b3eeba9a512051e8afa17c80a343168a0649
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268276
Commit-Queue: Zhi An Ng <zhin@chromium.org>
Reviewed-by: Bob Haarman <inglorion@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782751}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/dca7f0682577..883a4e449775

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC cmumford@google.com,eirage@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: cmumford@google.com,eirage@google.com
Change-Id: I8b7d353a0e4f549a0c43848ccb6a62893be9c5ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268465Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Reviewed-by: Chris Mumford <cmumford@google.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#782750}

The following histograms are still used, so this CL extends their
expiration:

OfflinePages.Background.EffectiveConnectionType.OffliningStartType*
OfflinePages.Background.EffectiveConnectionType.PauseRequests
OfflinePages.Background.EffectiveConnectionType.ResumeRequests
OfflinePages.Background.EffectiveConnectionType.RemoveRequests

Fixed: 1089124, 975187, 984193
Change-Id: I4a72645022e734f00ec4e42e799ca6cf009226e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268498
Auto-Submit: Scott Little <sclittle@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782749}

TBR=markbrand@google.com,mbarbella@chromium.org

Change-Id: I19c360fcf8638135eac3d1ee0eed9e4a4d882a20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268838Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782748}

When an extension is deactivated, SWTQ unregisters the extension's
worker. Subsequently, if the extension was re-activated quickly (which
is the typical e.g. from ExtensionApiTest::RunExtensionTest due to
kFlagEnableFileAccess), then it is expected that the unregistration
can fail (as the initial extension activation couldn't complete SW
registration). This CL doesn't log unregistration failure error
message in that case, removing confusion around the log.

Bug: None
Test: No behavior changes, spurious unregistration failed error shouldn't be seen from service_worker_apitest.
Change-Id: Ifccbc649b492f9cbe8527a5e6412cca2aea2d5ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2266016Reviewed-by: David Bertoni <dbertoni@chromium.org>
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782747}

This is part of the effort to use more respectful terms in our code.
I've also just restructured everything; there's no need to have it in
this weird directory structure. There are only 3 files.

Bug: 1097180
Change-Id: Ib599cc04bdf08e55fc8a3fbfdbdce4f7162f1acb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2264026
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782746}

These are monitored and used for pipeline health analysis.

Fixed: 1088903
Change-Id: Ieeb8696a411f4d62ae10e14e9e6def0fc9d0ad4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2264582
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782745}

http://crrev.com/c/2199934 introduces two scroll modes for omnibox in
omnibox-only variation. This CL makes trendy term section also adapt to
above scroll modes by combining the omnibox and the trendy term section
into one scroll component.

Bug: 1099037
Change-Id: I54016d78d3f90b2ed723ab4d0b46b0e7651113f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267844
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782744}

media/video-played-reset.html was previously failing on macOS, but is
now flaky on Linux (debug) so disabling the test.

Bug: 1010170
Change-Id: Ie4a46d27adfef2f18f7ee142986d814812ce2148
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268466Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Chris Mumford <cmumford@google.com>
Cr-Commit-Position: refs/heads/master@{#782743}

This patch adds the fully featured base unit test runner to the
openscreen_unittests binary, for fixing the linux-fieldtrial-rel bot.

Bug: b/159746216
Change-Id: Id6866d983e89b55e2e6f5ad707ced493d0d3b24e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261367Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Commit-Queue: Jordan Bayles <jophba@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782742}

As part of Feed development, add entry points to allow an XSurface
client to open a page in a new tab, open in an incognito tab, or
download the URL as an offline page.

Bug: 1099057
Change-Id: Id6152147c105993d88aa08cee9f16ea42da45b2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2265497Reviewed-by: Dan H <harringtond@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Reviewed-by: Jian Li <jianli@chromium.org>
Commit-Queue: Peter Williamson <petewil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782741}

This reverts commit 0403341d.

Reason for revert: AutotestPrivateApiTest.AutotestPrivate is failing

https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-dbg/19325

Apologies to developer if reverted in error.

Original change's description:
> Fix issue that webstore private APIs return array improperly
> 
> webstorePrivate.getExtensionStatus and requestExtension should return
> extension status as a string but not an array of string.
> 
> Bug: 1099334
> Change-Id: Ib56e466cc1d967e3a322494076ad7640a6868aac
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267719
> Commit-Queue: Owen Min <zmin@chromium.org>
> Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#782607}

TBR=zmin@chromium.org,karandeepb@chromium.org

Change-Id: Ibe7b886da11ee5864d3b8a73b8ed7d98f53327d6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1099334
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268839Reviewed-by: Chris Mumford <cmumford@google.com>
Commit-Queue: Chris Mumford <cmumford@google.com>
Cr-Commit-Position: refs/heads/master@{#782740}

Bug: 1028308
Change-Id: I95a678b69836418fb47c9bef3351653c4078329e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268303Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782739}

The following metrics are useful indefinitely. Mark them as never
expiring.

- Extensions.Functions.HandleResponseElapsedTime
- Extensions.Functions.StartRequestElapsedTime
- Extensions.UninstallType
- Extensions.InjectIdle_Time
- Extensions.InjectStart_BlockingScriptCount
- Extensions.InjectCssTime
- Extensions.InjectEnd_Time
- Extensions.InjectStart_ScriptCount
- Extensions.BadMessageFunctionName
- Extensions.BadSyncDataReason


Bug: 1088775, 1088788, 1088796, 1088785
Change-Id: I435883b798dfd5d06004b0d23231bc041f3077e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2265245Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782738}

https://android.googlesource.com/platform/external/perfetto.git/+log/f798f83c7a90..0d5f47eb1f8c

2020-06-25 fmayer@google.com Merge changes I07679156,Idd5df6ed,I5b52806a,Ifcc5608d

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel
Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I04a74a5b9582820b07fffd1e93abfaa88842df34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267924Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#782737}

Mock: http://go/e14s-emoji-suggestion-mock

Bug: 1099454
Change-Id: I7c048372185eddf0df4719288b61413378db2b25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268757Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: My Nguyen <myy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782736}

https://webrtc.googlesource.com/src.git/+log/e3296b6d4cb4..bf1816170b1f

2020-06-25 danilchap@webrtc.org In Av1 encoder propagate zero bitrate as inactive decode target

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: Ibff1f4dcb1c9f8e4cede2c6be0de814764f790c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268463Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#782735}

Bug: 1062736
Change-Id: I7ee810b21a120d0e45ccfa35c2c5e81cf7e57681
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267757Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Reviewed-by: Yao Xiao <yaoxia@chromium.org>
Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782734}

Enables dropping (through dragging) a URL into the content
area of the web view. Dropping the URL navigates the
web content to that URL.

This is controlled via a Finch feature flag.

Bug: 1099050
Change-Id: I10d1bb27eac4ce41811ace0af9a59fe12959183d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2248662
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782733}

This introduces the histogram PasswordManager.MoveUIDismissalReason,
similar to the existing ones for Save/Update. Like the Save one, it is
also split by PasswordAccountStorageUserState.

Bug: 1063852
Change-Id: I06a7c4e6522362a37b6092964f151eafd2f5d6b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2263815
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Auto-Submit: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782732}

This CL was split off from crrev.com/c/2253198.

Convert the following properties to use StyleColor instead of Color
in preparation for making system color keywords compute to themselves:
border-*-color
outline-color
column-rule-color
-webkit-text-emphasis-color
-webkit-text-fill-color
-webkit-text-stroke-color
-internal-visited-text-emphasis-color
-internal-visited-text-fill-color
-internal-visited-text-stroke-color

Bug: 1081945
Change-Id: I138545a294403019c2adfc6e292d2d18b0d8b0db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261190
Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782731}

Bug: 1066263
Change-Id: I4d59865d6595132896afc7c5db9fbd71d2d8a18c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268213
Commit-Queue: Evan Stade <estade@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Auto-Submit: Evan Stade <estade@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782730}

Bug: 1093135
Change-Id: Icaad5228194d5e55616f009c837df4ccfe7fca43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267745
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782729}

Previously we added a script write_ssargs.py to write .ssargs files for
SuperSize. To simplify things, this CL removes the script, and use GN
write_file() command instead.

As a result .ssargs files are created on "gn gen", instead of during
build.

Bug: 1040645
Change-Id: I147480817d1c3036780d5496cc30fd2d4c8b9fb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267337
Commit-Queue: Samuel Huang <huangs@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782728}

Bug: 1030649
Change-Id: Ie023fa418634466ad9bb40d659c02b8562840c2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249743
Auto-Submit: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782727}

To be used as owners for foo_lacros.{h|cc} files.

Bug: none
Change-Id: I6ec44e8de77659ffc4c2e47094a4af0e526b4a0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268178
Commit-Queue: James Cook <jamescook@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Auto-Submit: James Cook <jamescook@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782726}

There is legitimate case where a quad area can be larger than the
limits of int32_t (see bug).  Go over all calls to gfx::Size::GetArea
under viz. Handle overflow / underflow where it makes sense. Or
keeping calling GetArea where a crash makes sense.

Then remove the deserialization check that quad size does not
overflow.

Bug: 1067654
Change-Id: I00e11a753a299bc22a70a1b1891d6d5e348a0d05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2254531Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782725}

Adds an experimental setting in the debug section that sets values
for a few select policies when enabled. This is needed for manual
testing of the policy infrastructure.

The following policies are set:
​- Autofill​Credit​Card​Enabled:      NO
- ChromeVariations:               2
- DefaultPopupsSetting:           2
- DefaultSearchProviderEnabled:   YES
- DefaultSearchProviderSearchURL: http://www.google.com/?q={searchTerms}
- DefaultSearchProviderKeyword:   google
- PasswordManagerEnabled:         NO

Change-Id: I736df2215b0f0e47e90571698774a024fc8e828c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261223
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Reviewed-by: Owen Min <zmin@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782724}

Currently, native pages aren't animated during browser controls height
change animations. We change the margins to account for the change in
browser controls for these surfaces.

This CL adds browser controls animations for the NTP. As changing the
margins in every animation frame would cause a relayout and be
expensive, we use the translationY property to animate the page. The
margins are applied only once at the start or end of the animation.

Bug: 1075640
Change-Id: Ia376d3130f9c89210b64dec9c682138f08357f7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261108Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Sinan Sahin <sinansahin@google.com>
Cr-Commit-Position: refs/heads/master@{#782723}

What: Do not run the SF filter in DryRun mode on pages where the
content setting is set to allow.

How: Delete the ongoing activation throttle for the navigation when
we receive an explicit disabled activation state.

Currently we ignore disabled activation states when we receive them,
as normally the SF filter is running in DryRun mode anyway.


Change-Id: Ibc5202ec5f68bd284987cdd4d5dfa0e8de0708a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218371Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: John Delaney <johnidel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782722}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/30f774ef87bc..0bfbd890c3e2

2020-06-25 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Bug: None
Tbr: agable@chromium.org
Change-Id: Ib38063528ec32219a345554e62bc1e4b1b4fc884
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268457Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#782721}

TBR=yusufo@chromium.org, yuezhanggg@chromium.org

Bug: 1094998
Change-Id: I46bf61c10ea915eeff94ba58bf4f9aa501d3087d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268204Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Patrick Noland <pnoland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782720}

Bug: 1066556
Change-Id: Iefc809b03e76f6ccf579a9d1dec77118d4690fdb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261897
Commit-Queue: Hesen Zhang <hesen@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782719}

This is preparation step to add tap/click ability to accept suggestion.

Bug: 1098057
Change-Id: Ided9d81d99ca33b6d95a649b7545e238c0f4c865
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2257657Reviewed-by: Keith Lee <keithlee@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: My Nguyen <myy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782718}

This reverts commit a84e8b68.

Reason for revert: UI review thumbs down this change. We
sent a rebuttal, but i will first revert before branch. If
we get permission then its ok to punt to M86.

Original change's description:
> wm: Add display settings shortcut in context menu.
> 
> Details/mocks are linked in the linked bug.
> 
> Test: manual
> Bug: 1095140
> Change-Id: Ic8dc25d686355b80dc5f537eda67836e6c97f172
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225978
> Commit-Queue: Sammie Quon <sammiequon@chromium.org>
> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#778590}

TBR=xiyuan@chromium.org,sammiequon@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 1095140
Change-Id: I1d065a7d798e73a6151282d58d0843101d019ef4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268120Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782717}

Change-Id: I2e817334fb9b8988dacbd21b531090dd4574359d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2265353Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782716}

Bug: 1095643
Change-Id: Ibbe7862d6ded259612c795c9933d3b2a7bd7aef5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2264861
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782715}

Bug: 1084664
Change-Id: If89bc49be2d03710fe29d87675dbed3851dd84c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209396Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782714}

Fixed: 1089438,1097931,1097932,1097933,1097934,1097936
Change-Id: I470985b8b3f26d183a5924ef377ee6e3e83a9e8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261952
Auto-Submit: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782713}

Implements the HTTP APIs for Tachyon Express to send and receive
messages between devices. Tachyon would be used as the signaling
channel for webrtc messages in Chrome Sharing. The actual mojo
implementation and tying it to the utility process is upcoming in
the next CL.

Bug: 1082305
Change-Id: I62e1c3a2deb8a6ef376e474b5ce353a3cb863232
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250061
Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Alex Chau <alexchau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#782712}