issue_comments: 735431187
This data as json
| 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-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 |