Implement job policy ZX_POL_ACTION_KILL by calling
ProcessDispatcher::Kill from EnforceBasicPolicy.

Rename QueryBasicPolicy to EnforceBasicPolicy and tighten it by
marking as __WARN_UNUSED_RESULT.

Replace policy action bitfield with multiple choice.

Bug: ZX-3520 #comment done
Test: /boot/test/sys/policy-test
Change-Id: Ia6da570ebd8c4d81961f78d6ddcc643183f7c85c

We don't want to commit to APIs these files provide in sdk for now.

Change-Id: I2108af7b0c9614f6f71faa0adacc92f6b91773e1

Change-Id: I976512b86067fe7e473248451ec0f53b0ded6813

Test: No behavior change.
Change-Id: I2bf2ee8fb79faaab3c9fa1cf06ec0884a3510855

This just defines a new HandleBased Resource type to allow generated
Rust code for FIDL APIs that involve resources to build.
Resource-specific functions - like a wrapper for zx_resource_create -
are left for the future as needed.

Change-Id: Id43ea124258fcb29d0b7114f63175aca18176a80

Bug: BLD-447 #comment missing libraries
Change-Id: I07b1496df7fca40e673424755971a26156f9dfa4

The targets which are invoking pm_build_package directly (update.meta and
system_image.meta) are producing packages with incorrect names. This used to
be ignored due to bugs in the publish path that hid the problem, but those
were recently fixed highlighting this bug.

Test: fx build, observe "update" instead of "update.meta" package produced.
Change-Id: I947fa915e9ad7f35561ed463e03d79b61da2ebe0

Change-Id: Icf32a41695ad1f2bfaa54401dbc20b1d80b45211

The -d flag was altered some time ago to allow pointing at the repository
serving directory rather than the repository root. A recent regression caused
the interpretation to change, however, there is also now a discrepancy
between the meaning of -repo and -d. We now interpret -d to mean the
repository serving directory, and -repo to mean the repository root. As SDK
consumers are presently using -d, this restores the prior behavior for that
flag, while making the -repo flag behavior consistent across other commands.

Change-Id: I50d7567194101d3cf2c6af1bf83a33bc481f4290

Change-Id: Idd964e54b76efdfed0322f8f267a182f875efee2

TEST: fx shell 'ls \
/data/cache/r/sys/fuchsia.com:log_listener:0#meta:log_listener.cmx'

Change-Id: Ic1fe1a31ca10a51266c507bc67470ce335f2b561

This is the first step to implementing enums and enum-lists for the
setting system.

This is not hooked yet to the SettingStore, so it's possible to add
strings even though the schema doesn't allow it. As no setting uses this
functionality, that will be added in another CL for making reviewing
easier.

TEST=Added SettingSchema unit test.

Change-Id: I8376d9266c2fb3591576c9b14b5404db140cbd0b

Change-Id: I543f00f9b875e9e0e5cd929caaaf2e640d346372

This reverts commit bfed6f5c.

Reason for revert: On Thu, May 2, 2019 at 10:24 AM <...> wrote:
This change broke compile step in chromium with this error:
In file included from ../../third_party/fuchsia-sdk/sdk/pkg/fit/inclu
de/lib/fit/function.h:8:
../../third_party/fuchsia-sdk/sdk/pkg/fit/include/lib/fit/function_internal.h:183:63: error: declaration shadows a static data member of 'target<type-parameter-0-0, false, true, type-parameter-0-1, type-parameter-0-2...>' [-Werror,-Wshadow]
    static const void* target_type_id(void* bits, const void* ops) {
                                                              ^
../../third_party/fuchsia-sdk/sdk/pkg/fit/include/lib/fit/function_internal.h:209:46: note: previous declaration is here
    static const target_ops<Result, Args...> ops;
                                             ^
1 error generated.
See https://chromium-review.googlesource.com/c/chromium/src/+/1592429
I'm guessing this happens because chromium compiles this code as C++14 instead of C++17

Original change's description:
> [fit] Add a fit::callback "run once" variant of fit::function
> 
> To address fxb/ZX-3616
> 
> Test: fit-test
> Change-Id: I85d6454a07dd4a1578f608a6bac8f56b98b12a6d

TBR=jeffbrown@google.com,abarth@google.com,eieio@google.com,richkadel@google.com

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

Change-Id: Iba005018a0d86a64670d64d54e874f75ffdafccf

Change-Id: I93ed2ef4f7bc012c52fd35dfa3756438d9ac11df

Tested: No behavior changed; base_view_unittest
SCN-1291 #comment

Change-Id: I4631c9675a585bd32c328d9fdbb43b9c011beb98

Change-Id: Ifbd6ea250675805eb5de981ee1363267db6a8344

FIDL-600 #comment

Change-Id: I7d952cc1057cdf2d648f59614e108e8fb0ddd76f

Test: Boot on Astro.
Change-Id: I5772d8ef60b028c197764083ceb8a06cf48f407f

Change-Id: Ie3df76f1b93252a2ac9f7185291ff5eed2c309fe

currently with "-m" option netsvc.netboot is not getting set to true.
Bootimage for hikey is generated using mkbootimg and uses a separate
cmdline option. Fixed by passing the cmdline option to mkbootimg

TEST: Build zircon and flashed on hikey. Enabled init-ums usb option
./scripts/build-zircon-arm64 && ./scripts/flash-hikey -m
usbctl init-ums

Change-Id: I32e9d357591dbc466749ea316a313cd09b9f5dd0

TEST=Added and setup unittest. Tests pass.

Change-Id: Ida3771eb938d001ee0f260363fd50a91f3eee7cf

Before this change, blobfs-bench takes 5.3 minutes.  It covers 3*4=12
combinations of blob size and blob count.  The largest parameter
combination takes 3.7 minutes.  Skipping that combination reduces
blobfs-bench's overall runing time to 1.6 minutes.

Bug: PT-142
Test: garnet-x64-perf-dawson_canyon trybot
  + check time taken shown in bot log
Change-Id: I87845833708aa9100ead4ae2b22390be89a58c2e

Test: CQ

Change-Id: Iddd55a00153d217d0ca751880c20358b487a891a

Test: CQ

Change-Id: I137df55be5854170d07118056689c98d206babae

The top-level root Inspect object and the hub directory in which the
component's Inspect hierarchy is rooted are different things; they
should not share the same name and they definitely should neither one
have a name as unhelpful as "objects".

Change-Id: I9dfde478c0f29ad15a842ce3dddb538f1edb8b19

This logs the repository directory to assist in debugging OTA
test failures.

Change-Id: Idc7e3c8f5e579f803c073a5d58f8762880780c39

This reverts commit b63aff33.

Reason for revert: Breaking out-of-tree session shell

Original change's description:
> [scenic] Convert session_shell to ViewToken
> 
> Tested: No behavior changed; modular_tests, started story in sysUI
> SCN-1018 #comment
> SCN-1291 #comment
> 
> Change-Id: I8509501a15094d7d381557c186a9d0463488a956

TBR=mesch@google.com,thatguy@google.com,lindkvist@google.com,dworsham@google.com,pascallouis@google.com

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

Change-Id: I54697d9bb0b29e6e1b16644e8e379c12362fbf79

Change-Id: I6bcdf169f8db3246911a47726373fc7190dc46a8

Change-Id: I15ca5558b5e25c2189cfa68ec2ea57685349e8d8

The package server can now, if auto is enabled and a package manifest list is
provided, automatically publish the given packages. It will also monitor them
for updates and continually publish them as they are updated.

Test: test coverage at end of patch series
Change-Id: Ia19d4e738b8db0f537428924b15069746a90033c

This is preparation work for an ephemeral server based on the package output
manifests, which will introduce a new serve subcommand that shares much of
this code, but watches more files.

Test: tests are added at the end of the patch chain, due to being missing previously.
Change-Id: Ifebc55e5052392a8744c8d6291a4d59e806e855c

The package build tool now produces a JSON manifest as an output format that
is usable as a complete input specification for a publish operation. The
expand tool also produces this manifest. The build passes this to the new
publish operation to perform all publishing.

Test: publish tests are backfilled later in patch series
Change-Id: Ifae5a70d07143a86ec19b1c68a8625151db2eb71

Added GATT server-role support for the ATT Prepare Write
and ATT Execute Write requests.

Bug: BT-89 #done
Test: bt-host-unittests --gtest_filter=GATT_ServerTest*

Change-Id: Ide75e59fb9e972a0fb98f9e409ceaf210ae36429

Bug: DX-1238 #done
Change-Id: I097a8dae3de136e743a5e40fd37d96a77b76e8c7

Test: fx serial /dev/ttyUSB0
Change-Id: Ib35a0ddcd07a52c380f15e0364d4430bb1e22c87

Change-Id: I1eb66949600e15fe979a73ad482aa6faa77c52c3

Change-Id: I5e2fb6f3af76eed482ff6fe69684b9c5ceadfd7e