Reland "Re-enable the Dart Development Service (DDS) (#64671)"#65873
Conversation
|
cc @mehmetf: tested both failures we were seeing in google3 (coverage and run) and we seem good to go. Will let you know when this lands so we can keep an eye on things once it makes it into google3. |
|
Could we roll the latest version of dds into g3 first so that the google testing shard can be up to date? |
Yup, already done. Re-running the testing shard now. |
…_prebuilt_test.dart Co-authored-by: Jonah Williams <jonahwilliams@google.com>
|
This pull request is not suitable for automatic merging in its current state.
|
PR #65873 enabled DDS for non-web Flutter applications. This change surfaced a bug where DDS would not send ServiceRegistered events to VM service clients when they subscribed to the Service stream. This would cause tools and tests that rely on these events (e.g., hot reload in VSCode) to fail. Fixes #66038.
PR #65873 enabled DDS for non-web Flutter applications. This change surfaced a bug where DDS would not send ServiceRegistered events to VM service clients when they subscribed to the Service stream. This would cause tools and tests that rely on these events (e.g., hot reload in VSCode) to fail. Fixes #66038.
|
This has broken the Here's the full log: How can this be fixed, @bkonyi ? |
|
@liyuqian I'll investigate and get back to you with a fix today. |
PR flutter#65873 enabled DDS for non-web Flutter applications. This change surfaced a bug where DDS would not send ServiceRegistered events to VM service clients when they subscribed to the Service stream. This would cause tools and tests that rely on these events (e.g., hot reload in VSCode) to fail. Fixes flutter#66038.
Changes from last attempt:
--host-vmservice-portto be used by DDS as this breaks google3 remote workflows.--dds-portto allow specifying the port that DDS will bind to. If not provided, a random port is chosen.