This reverts commit 75b35cea.

Reason for revert: This CL is a suspect for the currently red fuchsia-roller;  it fails the /boot/test/ddk/platform-bus-test test.

Original change's description:
> [devcoordinator] Fix buggy composite device behavior
>
> If a component was a device with MUST_ISOLATE set on it, we would try to
> bind to the non-proxied side of it, which doesn't speak the device
> protocols.
>
> Change-Id: I64eaccec5d51997f4374d0277b040a952f681667

TBR=teisenbe@google.com,abarth@google.com,jocelyndang@google.com

Change-Id: Id9d48682336ea648599cfead60444c5074c4ae1e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true

This entailed another substantial cleanup of environment_redirect()
to handle more cases.  It also necessitated reorganizing the deps
in the Zircon build for the legacy integration.  The new arrangement
should be much easier to understand.

Bug: BLD-447 #comment Fixed --variant asan build
Test: fx set bringup.x64 --variant asan && fx build
Change-Id: I2cd8d7aa95eba5f34af421c75d634f31d988a1f8

Test: $ runtests /pkgfs/packages/wlan-hw-sim-tests/0/test
ZX-3496 #done

Change-Id: I52e861590cda6720b22577cb6b9496d5ed68ddec

[Still in progress, please do not review yet]

Change-Id: Ifa4641b3a5e48091aac1e10d9052dfb927aa962c

Missing a link; created an external one to Chromium docs as a placeholder

Change-Id: I352b559f728a8fbedda334cb72746538a5937ff3

Do not export inline functions or methods.

Bug: ZX-1895
Change-Id: I54b8385d92507dc7b3792efe3a3ddba6c82055da

Bug: MTWN-273 #comment
Change-Id: Ib2e5a329a052b17ec40aa3a36578d65c269fb6b0

Create ownership wrapper for StreamOp with move semantics to make
obvious where it is currently owned.

Change-Id: Id882616bfe4a5fb6f77f50277f996e81963917d1

TEST: builds
Change-Id: Ic4ed3cd29521d78363d38c0444a2324f0f2aee4a

These deprecated scripts are no longer used.

Bug: BLD-424 #done
Change-Id: If5b9107c024d0b1154d0e35231fc47214f58d12a

Creating meta.far archives for Fuchsia packages will involve adding
several small files to the archive. With this change, we'll be able
to create these small files only in memory instead of needing to
round-trip through disk.

Changed the input iterator trait object to a BTreeMap to disallow
duplicate package paths at the call site.

Change-Id: Iab0c641ea1719c477105d0ec7431f4dcfa7b1bd8

This makes basemgr_launcher available to the sdk image by including it
in the modular tools package.

MF-257 #comment Add basemgr_launcher to modular tools package

Change-Id: Idbdf7788f64796bf500a3b2876c6dd459f4f8810

Currently, ACTS tests are triggered through a custom recipe - fuchsia_connectivity_hacky.py.
Now that HTI (Host Target Interaction) tests are supported in our infra,
we can rewrite the ACTS runner in Dart and eventually migrate to the standard fuchsia.py recipe.

For comparison, here is the current Shell script runner that's triggering BT ACTS tests:
https://paste.googleplex.com/6213748912029696.

Bug: IN-831 #comment

Change-Id: Ib0abdfbeb77cff9557288364445266d045eb8550

If a component was a device with MUST_ISOLATE set on it, we would try to
bind to the non-proxied side of it, which doesn't speak the device
protocols.

Change-Id: I64eaccec5d51997f4374d0277b040a952f681667

This adds the configuration that specifies if stories should use new runners or
reuse their parents' runners.

MF-353 #comment Add story_realm_inherit_parent_runner config and update docs
TEST=fx run-test peridot-tests

Change-Id: Ifed85a9dacce34db614a5e7fda82e5da3d23630d

replace "two" with "three" prior to list of three items.

Test: none.
Change-Id: I947a4dfa7cd56af8a9abca43b10273984211b460

Failure to communicate with a test server peer caused both the test
runner and the go and c++ test servers to just hang. They should (and
now do) fail loudly.

Change-Id: Ic8116045935a45c1fca19cffdf80a39abf343531

When a memfs is created without an explicit max page limit, the fs
assumes UINT64_MAX, which is confusing when manifested in
QueryFilesystem calls. This patch refines the cap to the amount of
available physical memory.

Test: /boot/test/fs/memfs-test
Change-Id: I10fada0b8b2eb7b33f270cd31c9d859157475c1d

This change creates the new libiquery library and implements the first
part of it: Discovery.

Follow ups will include: Reading, Formatting

CF-714: #progress

Change-Id: I4bc6af3367ef8030479bd722c8b4462cef981764

During end to end testing, the system load on some devices may be
high enough to cause the scheduler to not give audio_core another
time slice, leading to UNDERFLOW conditions.  This is causing
failures in CI.

BUG: MTWN-269
TEST: Ran end to end test repeatedly with no failures.
Change-Id: I3b0cc24140b88bf9315abddf59a461491d504d53

missing. Added a unit test that failed without the changes.

Change-Id: Idaf9913bf9006384e021f39047df1e8e8a855369

* it turns out async::PostDelayedTask returns a status so we might as well log an error if we couldn't post the timeout!

TESTED=I don't know an easy way to make the async loop reject the task :-(

Change-Id: I99b3a685f8ac2176aa0274890bc2a51e6661ce91

Test: CQ

Change-Id: I5e8322db78c313bad9af2a71759cdf6e71dbd0c9

Following earlier discussions with Satsuki the precedent we set with
these packages didn't make sense when applied to token manager. We're
probably stomping on a wider namespace than we'd ideally like but thats
a common theme across rust package names at the moment plus its
possible we'll roll both these into token manager at some point anyway.

Change-Id: I825ca9e0a853cdafde845e96077a64d1d5729bc4

Implements ZX_JOB_TERMINATED, which is signaled when a job is killed,
after all its children have finished cleaning up.

This also changes job tracking behavior. Previously, if a job was killed
it would stay in the job trees until the last handle was closed. With
this patch, jobs now behave like threads or processes and remove
themselves from the task trees as soon as they (and all children) have
been killed. This provides a more consistent behavior among all tasks.

As a nice side-effect, now if a job fails to create (e.g. if the parent
is already dead) we never add it to the all-jobs tree; previously it
would be briefly added and then removed.

ZX-3919

Test: runtests
Test: run-zircon-x64 -C -b -k -z core-tests-x64.zbi
Change-Id: Ic367b7df9704e5012a1c73636d76784c527a4636

It has been replaced by the //sdk/bundles:tools set of packages.

Bug: DX-1269
Change-Id: I49e1cf26ede67ac15da06b813b90968b25e7e010

This reduces the externally and internally mutable surface of the datastructure

Change-Id: I26f045a62cfa2bd78c3c02a65ee0c4b062f9c6f3

Component manager will not always be able to rely on
fuchsia.logger.LogSink being present in its namespace, so this commit
adds new logging macros to src/log.rs to log to zircon's debuglog. If
debuglog creation fails, logs are sent to stderr.

CF-707 #done

Change-Id: I5893719e6bb72aaba481ac0a0cbe43911cfea29c

...reading fuchsia.netstack.NetInterface{,2}.Ipv6addrs from upstream and
removing netiface.NIC.Ipv6addrs, which is no longer referenced.

NET-1181 #done
NET-1223 #progress

Change-Id: I4fee8d2d144b705e8643b3f9d73075a00d5e1fb1

This method has been deprecated for a while and is now unused.

Bug: ZX-2620 #done
Change-Id: I742ca8299a598000b34aaee17c2493a441db6076

This CL moves the CopyArrayToVector from sandbox.cc's anonymous
namespace to a helper method in json_parser.cc, and updates the
callers to use it as appropriate.

Bugs: CF-723

Tests: fx run-test json_unittests
Change-Id: I8546d76eeec621c0c5539521b7c000f534e95e15

Change-Id: I706db37f1aba1d62d56bc649cb4a69f149a59c76

Change-Id: I907aeffc7303998b136a59c63327badf42fc08e5

Mozart no longer exists, as a project or a team.  It's nice to not have
it show up when grepping the code-base.

Tested: CQ; no behavior change
SCN-580 #comment

Change-Id: I5456c927e7fdf63be820a970f04636c9345db64b

Use ZX_INFO_THREAD and thrd_join to eliminate races.

Use test infrastructure's timeout rather than a test specific timeout.

Change-Id: Ib25a5a1c54ea5a358c863202447c38706746207a

FLK-168 #progress

Change-Id: I4b049fb145d88bc3f028e7bb6665a36634418f4d

BUG: FLK-178 #progress

- Disable SandboxTest.DestructorRunsCleanly. Race condition causing
flakiness.

Change-Id: Ia7115f536d3f4a0b25e0deced2ab8f0133c3a69e

Change-Id: I3413b9b5d910e3f695437a8622d61cf821158603

* Update the location of the dart-sdk
* Add more troubleshooting tips

Change-Id: Iba475bd1505e390dd022a163a75ee91e3f1c4365

... and support --detach with spawned apps.

PT-141 #done

Change-Id: If980b4e8227d72e7c94af022ad344b374b09e335