| commit | ca4244a25cc45c94dcda0ff45c6832e4bd3c70c3 | [log] [tgz] |
|---|---|---|
| author | Charles Celerier <chcl@fuchsia.infra.roller.google.com> | Thu Mar 27 20:49:21 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 27 21:02:34 2025 -0700 |
| tree | 9b1644d550ededd70a0b7340a13cc71ac5466484 | |
| parent | 955d2a0cebd3bbe79f95dd90b25f595f8711aa86 [diff] |
[roll] Roll fuchsia [fidl][python] Don't panic on unsupported struct types (but still don't support them)
While compiling a struct, it's possible fidlgen_python may encounter
types or attributes Python bindings don't support. Instead of panicking
while compiling, bindings will still be compiled. The structs with
unsupported aspects will compile to a type that can't be constructed.
This allows compiling FIDL libraries which may contain some types that
aren't supported but don't need to be used.
An example runtime error looks like this
```
NotImplementedError: test.constants/Struct not supported.
- int64_with_default annotated with allow_deprecated_struct_defaults
- string_with_default annotated with allow_deprecated_struct_defaults
- bool_with_default annotated with allow_deprecated_struct_defaults
- enum_with_default annotated with allow_deprecated_struct_defaults
- bits_with_default annotated with allow_deprecated_struct_defaults
```
Test: Verify plumbing works when compiling an unsupported attribute.
Original-Bug: 355717613, 404845645
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1231924
Original-Revision: c9ef546a150618576c5603abed3c46f90383d526
GitOrigin-RevId: d1dac30816d33772347dfc0aaa14f34d8b9d617b
Change-Id: I157d86eaa4ee990af44fe0b157b39ddb02c39d6a
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 in one of the communication channels documented at get involved.
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.