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/4842#issuecomment-769198581,https://api.github.com/repos/pydata/xarray/issues/4842,769198581,MDEyOklzc3VlQ29tbWVudDc2OTE5ODU4MQ==,1217238,2021-01-28T16:18:16Z,2021-01-28T16:18:16Z,MEMBER,We should probably be pulling xarray's `nbytes` from `nbytes` attribute on arrays. Then at least we can leave this calculation up to the backend array.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,793245791
https://github.com/pydata/xarray/issues/4842#issuecomment-766732368,https://api.github.com/repos/pydata/xarray/issues/4842,766732368,MDEyOklzc3VlQ29tbWVudDc2NjczMjM2OA==,4160723,2021-01-25T10:56:05Z,2021-01-25T10:56:05Z,MEMBER,"I guess it could be possible to do a typecheck for this case. It's tricky to have a smart `nbytes` that works in all cases, though. For example, it's not really possible to get this information for dask arrays with sparse chunks (https://github.com/dask/dask/issues/5313).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,793245791