issue_comments
6 rows where issue = 646038170 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Unable to decode a date in nanoseconds · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1112047474 | https://github.com/pydata/xarray/issues/4183#issuecomment-1112047474 | https://api.github.com/repos/pydata/xarray/issues/4183 | IC_kwDOAMm_X85CSH9y | spencerkclark 6628425 | 2022-04-28T10:34:20Z | 2022-04-28T10:34:20Z | MEMBER | This issue was addressed as part of https://github.com/pydata/xarray/pull/4684. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unable to decode a date in nanoseconds 646038170 | |
1111612658 | https://github.com/pydata/xarray/issues/4183#issuecomment-1111612658 | https://api.github.com/repos/pydata/xarray/issues/4183 | IC_kwDOAMm_X85CQdzy | stale[bot] 26384082 | 2022-04-28T00:37:43Z | 2022-04-28T00:37:43Z | NONE | In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here or remove the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unable to decode a date in nanoseconds 646038170 | |
685200043 | https://github.com/pydata/xarray/issues/4183#issuecomment-685200043 | https://api.github.com/repos/pydata/xarray/issues/4183 | MDEyOklzc3VlQ29tbWVudDY4NTIwMDA0Mw== | hmaarrfk 90008 | 2020-09-02T00:13:30Z | 2020-09-02T00:13:30Z | CONTRIBUTOR | i ran into this problem trying to round trip time to the nanosecond (even though i don't need it, sub micro second would be nice) but unfrotunately, you run into the fact that cftime doesn't support nanoseconds https://github.com/Unidata/cftime/blob/master/cftime/_cftime.pyx Seems like they discussed a nanosecond issue a while back too https://github.com/Unidata/cftime/issues/77 Their ultimate point was that there was little point in having precision down to the nano second given that python datetime objects only have microseconds. I guess they are right. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unable to decode a date in nanoseconds 646038170 | |
651851046 | https://github.com/pydata/xarray/issues/4183#issuecomment-651851046 | https://api.github.com/repos/pydata/xarray/issues/4183 | MDEyOklzc3VlQ29tbWVudDY1MTg1MTA0Ng== | jthielen 3460034 | 2020-06-30T15:01:27Z | 2020-06-30T15:01:27Z | CONTRIBUTOR |
Nanoseconds (and seconds with any other SI prefix from yocto to yotta) are indeed valid in the CF conventions. For reference, there is this table in v1.8 of the conventions, as well as the SI prefix and SI base unit databases of UDUNITS. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unable to decode a date in nanoseconds 646038170 | |
651404825 | https://github.com/pydata/xarray/issues/4183#issuecomment-651404825 | https://api.github.com/repos/pydata/xarray/issues/4183 | MDEyOklzc3VlQ29tbWVudDY1MTQwNDgyNQ== | shoyer 1217238 | 2020-06-29T22:34:35Z | 2020-06-29T22:34:35Z | MEMBER | We would absolutely accept a pull request for this, but I'm not 100% sure that nanoseconds are valid per CF conventions. CF conventions references udunits.dat, which as far as I can tell includes no units smaller than 1 second: https://www.unidata.ucar.edu/software/udunits/udunits-1/udunits.txt |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unable to decode a date in nanoseconds 646038170 | |
651370968 | https://github.com/pydata/xarray/issues/4183#issuecomment-651370968 | https://api.github.com/repos/pydata/xarray/issues/4183 | MDEyOklzc3VlQ29tbWVudDY1MTM3MDk2OA== | dcherian 2448579 | 2020-06-29T21:15:17Z | 2020-06-29T21:15:17Z | MEMBER | Thanks @fbriol . We would happily take a PR for this. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unable to decode a date in nanoseconds 646038170 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 6