[roll] Roll fuchsia [ffx][emu] Only generate a vsock CID if config value is 0

Right now we unconditionally overwrite whatever value is provided in the
config. While the user in most cases wouldn't care what value ends up
being used, it's strange to have this behaviour while exposing it as a
knob in the config. Accordingly, we update the default as 0 (an invalid
CID) and only overwrite it in that case. If any non-zero value is
provided, then that's the user intended and that's what the user will
get.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1227674
Original-Revision: 42bac5d1a3293446c474e321aa9ca870fb5d6eec
GitOrigin-RevId: 77e3488b9a5a6d88c2afdf43a8a41159b1c35860
Change-Id: I9a15c45a36336db78bc1ee44679a6c5866f259b7
1 file changed
tree: ec08326adc9db8354d8b6353c1f85051d16da45f
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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 in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.