[roll] Roll fuchsia [exceptions] Keep report request lambda in scope Change from explicitly connecting to `fuchsia::feedback::CrashReporterPtr` to using `OneShotCall`. This will prevent the lambda from going out of scope so we can actually perform work based on the result of the crash report filing request. Original-Bug: 122421 TESTED=`fx test exception_broker_unittest` TESTED=`fx shell crasher` @ 3b701b71a6a33946 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/812185 Original-Revision: d223b04e74a21d36b1fb5aedbf2386f418517bac GitOrigin-RevId: d219da06e433f7958a46964a6daa20e31d5d83df Change-Id: Ia4b40f14c5e8a7a44587a46afea2d1dc4d710bc2
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.