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/7132#issuecomment-1302325806,https://api.github.com/repos/pydata/xarray/issues/7132,1302325806,IC_kwDOAMm_X85Nn-ou,12818667,2022-11-03T15:58:13Z,2022-11-03T15:58:13Z,NONE,"@dcherian Thanks; I agree that this seems to be the same as #7028. Just as a note, I have had 3 people reach out to me (1 from UNH, 2 from across the globe) thanking me for the work around in my message. So this does seem to be a commonly encountered issue. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1397532790
https://github.com/pydata/xarray/issues/7132#issuecomment-1288188522,https://api.github.com/repos/pydata/xarray/issues/7132,1288188522,IC_kwDOAMm_X85MyDJq,1217238,2022-10-23T19:59:28Z,2022-10-23T19:59:28Z,MEMBER,"This is correct -- `CFDatetimeCoder.encode` is not lazy, even if the inputs are Dask arrays.

We would welcome contributions to fix this. This would entail making the `encode` look similar to the `decode` method (using `lazy_elemwise_func`).

We would also need a fall-back method for determining appropriate time units without looking at the array values. Something like `seconds since 1900-01-01T00:00:00` would probably be a reasonable choice.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1397532790