html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/7813#issuecomment-1535108194,https://api.github.com/repos/pydata/xarray/issues/7813,1535108194,IC_kwDOAMm_X85bf-Ri,35968931,2023-05-04T17:07:15Z,2023-05-04T17:07:15Z,MEMBER,"> If you hover over a node in the SVG representation you'll get a tooltip that shows the call stack and the line number of the top-level user function that invoked the computation. Does that help at all?

That's neat!

> When you create a dask graph of xarray operations, the tasks in the graph get useful names according the name of the DataArray they operate on

I realise now that this is not true - but can we make it true for cubed in xarray? Using cubed with xarray creates array's with names like `array-002`, but couldn't we use the dataarray's `.name` attribute to give this node of the graph the name `""U""` for example? 

> BTW should this be moved to a cubed issue?

I raised it here because it relates to an unfinished part of #7019 - where there is still dask-specific logic for naming individual tasks. I think that to solve this we will need to alter xarray code to allow `ChunkManager` objects to decide how they want to name their tasks, but using information passed from xarray (i.e. `DataArray.name`).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1694956396