PSA: Ongoing FIDL wire format migration

23 views
Skip to first unread message

Benjamin Prosnitz

unread,
Jan 25, 2022, 1:58:27 PM1/25/22
to fidl-dev, anno...@fuchsia.dev
TL;DR: FIDL is migrating to a new wire format. No action is needed on your end.

FIDL is switching to a new wire format, implementing the following RFCs:
- RFC-0113: Efficient Envelopes
- RFC-0114: Inlining small values in FIDL envelopes

This migration will take place on a binding by binding basis. I will reply here when the "on" switch is flipped in each binding.

If you see any issues that you think might be related to this migration, please reach out to me.

Benjamin Prosnitz | Software Engineer | bpro...@google.com

Dan Johnson

unread,
Jan 25, 2022, 2:47:02 PM1/25/22
to Benjamin Prosnitz, fidl-dev
Is persistent fidl as used in component manifests affected by this migration? If so, how long will component_manager continue to be able to read the old manifests?

--
All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
---
You received this message because you are subscribed to the Google Groups "announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to announce+u...@fuchsia.dev.
To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/announce/CAFeT2mgTAxTJahZWffEm-Le2gmeS-Tk%2BvrZcSUjrg%3DRQOm3FJw%40mail.gmail.com.

Benjamin Prosnitz

unread,
Jan 25, 2022, 3:03:01 PM1/25/22
to Dan Johnson, fidl-dev
Persistent FIDL is not affected by the current roll out, but for the migration to the new wire format to be fully completed usages of persistent FIDL will need to eventually migrate over.

Given the variety of usages of persistent FIDL, this will need to be done on a case-by-case basis and may take some time to complete. This work has not started yet.

Benjamin Prosnitz | Software Engineer | bpro...@google.com

Benjamin Prosnitz

unread,
Jan 25, 2022, 3:47:37 PM1/25/22
to fidl-dev, anno...@fuchsia.dev
Encoding of the new wire format in transactional messages is now enabled in:
- HLCPP after the submission of fxrev.dev/582221

Benjamin Prosnitz | Software Engineer | bpro...@google.com

Benjamin Prosnitz

unread,
Jan 26, 2022, 3:46:12 PM1/26/22
to fidl-dev, anno...@fuchsia.dev
Encoding of the new wire format in transactional messages is now enabled in:
- LLCPP after the submission of fxrev.dev/637361
HLCPP after the submission of fxrev.dev/582221

Benjamin Prosnitz | Software Engineer | bpro...@google.com

Benjamin Prosnitz

unread,
Feb 1, 2022, 3:31:24 PM2/1/22
to fidl-dev, anno...@fuchsia.dev
Encoding of the new wire format in transactional messages is now enabled in:
- Dart after the submission of fxrev.dev/582301
- Rust after the submission of fxrev.dev/585441
- Go after the submission of fxrev.dev/636547
- LLCPP after the submission of fxrev.dev/637361
- HLCPP after the submission of fxrev.dev/582221

This concludes flipping the "on" switch in each binding. Once rolls complete, the new wire format will be used for writes everywhere.

Once again, please let me know if you encounter any issues that you suspect might be related.

Benjamin Prosnitz | Software Engineer | bpro...@google.com

Reply all
Reply to author
Forward
0 new messages