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/pull/4400#issuecomment-1484222279,https://api.github.com/repos/pydata/xarray/issues/4400,1484222279,IC_kwDOAMm_X85Yd29H,90008,2023-03-26T20:59:00Z,2023-03-26T20:59:00Z,CONTRIBUTOR,nice!,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-1484209092,https://api.github.com/repos/pydata/xarray/issues/4400,1484209092,IC_kwDOAMm_X85YdzvE,2448579,2023-03-26T20:08:50Z,2023-03-26T20:08:50Z,MEMBER,"The merge conflict suggests this was fixed on main by #4684
","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-735777126,https://api.github.com/repos/pydata/xarray/issues/4400,735777126,MDEyOklzc3VlQ29tbWVudDczNTc3NzEyNg==,2418513,2020-11-30T13:12:47Z,2020-11-30T13:12:47Z,NONE,"Yea, well, in this case it's not about Python... `M8[ns]` datatype is simply an `int64` underneath, why not just store it as that, no bells and whistles required, no corruption possible, no funky conversions?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-735759416,https://api.github.com/repos/pydata/xarray/issues/4400,735759416,MDEyOklzc3VlQ29tbWVudDczNTc1OTQxNg==,90008,2020-11-30T12:33:33Z,2020-11-30T12:33:33Z,CONTRIBUTOR,"I think you should be able to define your own custom encoder if you want it to be a datetime.

But inevitably, you will have to define your own save and load functions.

Python, by definition of being such a loose language, allows you to do things that the original developers never really imagined.

this can sometimes lead to silent corruption.like the one you've experienced.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-735431187,https://api.github.com/repos/pydata/xarray/issues/4400,735431187,MDEyOklzc3VlQ29tbWVudDczNTQzMTE4Nw==,2418513,2020-11-29T17:52:37Z,2020-11-29T17:52:37Z,NONE,"I'm working on an application where nanosecond-resolution is critical and took me days to find why my timestamps are all scrambled or off-by-1 after I write them with xarray and them read them back... would probably much rather prefer if it threw an exception instead of corrupting your data silently. 

Non-standard netcdf or not, if it was possible to just store them as plain int64s and read them back as is, that would help a ton...","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-735430231,https://api.github.com/repos/pydata/xarray/issues/4400,735430231,MDEyOklzc3VlQ29tbWVudDczNTQzMDIzMQ==,2418513,2020-11-29T17:45:14Z,2020-11-29T17:45:14Z,NONE,"I think netcdf lists ""nanoseconds"" as a valid unit though?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-735428578,https://api.github.com/repos/pydata/xarray/issues/4400,735428578,MDEyOklzc3VlQ29tbWVudDczNTQyODU3OA==,90008,2020-11-29T17:32:37Z,2020-11-29T17:32:37Z,CONTRIBUTOR,"yeah, i'm not too sure. I think the idea is that this breaks compatibility with netcdf times, so the resulting file is thus not standard.

For my application, us timing is enough.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-734963454,https://api.github.com/repos/pydata/xarray/issues/4400,734963454,MDEyOklzc3VlQ29tbWVudDczNDk2MzQ1NA==,2418513,2020-11-27T19:38:47Z,2020-11-27T19:38:47Z,NONE,But the test already passes (i.e. you can at least do a `.encoding={.... 'nanoseconds'}` and avoid float conversion?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-734962866,https://api.github.com/repos/pydata/xarray/issues/4400,734962866,MDEyOklzc3VlQ29tbWVudDczNDk2Mjg2Ng==,2418513,2020-11-27T19:36:02Z,2020-11-27T19:36:02Z,NONE,"Oh, that requires `cftime._cftime` support first? :/","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795
https://github.com/pydata/xarray/pull/4400#issuecomment-734962563,https://api.github.com/repos/pydata/xarray/issues/4400,734962563,MDEyOklzc3VlQ29tbWVudDczNDk2MjU2Mw==,2418513,2020-11-27T19:34:48Z,2020-11-27T19:34:48Z,NONE,Is there anything preventing to merge this? ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,690546795