Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Dev Tools - Network monitoring for Isolates #2189

Open
NightOwlCoder opened this issue Jul 17, 2020 · 3 comments
Open

New Dev Tools - Network monitoring for Isolates #2189

NightOwlCoder opened this issue Jul 17, 2020 · 3 comments
Labels
needs-more-details Issues that need more details before they can be triaged P3 issues we think are valid but not important screen: network Issues with the Network screen.

Comments

@NightOwlCoder
Copy link

Hey there guys,

just saw the new Dart Tools on Flutter Days 2020, and went straight to my app, as for a long time I need a "log" of all the network calls.

What a disappointment to learn that Isolates calls do no appear.

Is this "my app" or is it not supported?

And thank you all for such amazing tools.

@jacob314 jacob314 added the screen: network Issues with the Network screen. label Jul 20, 2020
@jacob314
Copy link
Contributor

Fyi @kenzieschmoll

@kenzieschmoll
Copy link
Member

From @bkonyi

I don't think this would really fit with the networking page. It might be worth investigating putting this functionality on a dedicated isolate page (I plan on porting some sort of isolate page from Observatory anyway). Here we could display all isolate related information, including recent inter-isolate messages, open ports (useful when trying to determine why an isolate isn't shutting down), and potentially outstanding asynchronous calls / zone information.

We'd need to add support for a lot of the features above, but it should be doable. Currently there's no monitoring of inter-isolate communication traffic exposed through the service, but you can get this information in human "readable" format by passing --trace-isolates to a debug build of the VM.

@devoncarew devoncarew added this to the Backlog milestone Jul 31, 2020
@kenzieschmoll kenzieschmoll removed this from the Backlog milestone May 24, 2022
@kenzieschmoll kenzieschmoll added P3 issues we think are valid but not important and removed P5 labels Jul 5, 2023
@srawlins
Copy link
Contributor

srawlins commented Feb 6, 2025

@NightOwlCoder sorry for the extreme delay. Do you mean the calls between isolates, on SendPort/RecievePort objects, or network calls made from child isolates / isolate groups?

@srawlins srawlins added the needs-more-details Issues that need more details before they can be triaged label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-more-details Issues that need more details before they can be triaged P3 issues we think are valid but not important screen: network Issues with the Network screen.
Projects
None yet
Development

No branches or pull requests

5 participants