Bryce Huang

@mattip The actor table will try to load data by calling the `/logical/actors` endpoint defined in `actor_head.py` ([code](https://github.com/ray-project/ray/blob/856453f2648d08d3373531ac16de4bf7b7722acf/dashboard/modules/actor/actor_head.py#L243C1-L244C1)). Could we collect some data by calling the endpoint `localhost:8265/logical/actors` directly?

hmm that's a bit surprising since I expect having some data like `state: ALIVE` at least

The endpoint will collect `processStats` [here](https://github.com/ray-project/ray/blob/856453f2648d08d3373531ac16de4bf7b7722acf/dashboard/datacenter.py#L231), and the source of the data is from `reporter_agent.py` -- which were the places we looked during the debugging

Tracing the gap between `reporter` and the `DataSource` -- I think this is where the data get filled into DataSource: https://github.com/ray-project/ray/blob/856453f2648d08d3373531ac16de4bf7b7722acf/dashboard/modules/reporter/reporter_head.py#L649

I think the next step will be digging into the `reporter_agent.py` to see whether the metrics are read from psutil correctly

The summary looks good! When I was debugging ray python files, I sometimes need to restart ray cluster to see the updated code by `ray stop; ray start --head`. Maybe...

Distributed debugger currently cannot custom the debugging ports. I think we could solve this in two steps: 1. let debugger only use a fixed range of port numbers, e.g. 50000...

@rmhowe425 Thanks for reporting and taking this issue. I assign the issue to you, but please feel free to drop the assignment if you decide not to commit the PR....