[roll] Roll fuchsia [input] Validate the well-formedness of KeyEvent

The commit at fxr/573576 started enforcing timestamps on `KeyEvent`s
forwarded by the IME service to clients. This was an improvement over
prior state of the art but didn't go far enough.

This change adds verification on the fields `type_`, `key` and
`key_meaning`.  If we forward `KeyEvents` that don't have them this is a
bug, so we crash with an appropriate error message.  I don't think it is
possible to make this check happen at compile time.

Original-Bug: 83632
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/575246
Original-Revision: d665cccfc02406f437d742adbc0455eb9e6366f1
GitOrigin-RevId: acc8ee9a2ae95f484da2c6657688d681cfe34345
Change-Id: Iabf480f9a80a556324641d7be0c83e149334626d
1 file changed
tree: ae06b9d7914783f6cf9159f1501d85f7a122b134
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
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 via the IRC channel #fuchsia on Freenode.

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.