issue_comments
1 row where issue = 646038170 and user = 90008 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 · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
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 |
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 1