issue_comments
3 rows where author_association = "MEMBER", issue = 99836561 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- time decoding error with "days since" · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
129198927 | https://github.com/pydata/xarray/issues/521#issuecomment-129198927 | https://api.github.com/repos/pydata/xarray/issues/521 | MDEyOklzc3VlQ29tbWVudDEyOTE5ODkyNw== | jhamman 2443309 | 2015-08-09T15:29:52Z | 2015-08-09T15:29:52Z | MEMBER |
I agree, although that sounds like quite an undertaking. Maybe raise an issue over at numpy and ask if they would be interested in a multi-calendar api? If numpy could make it work, then I'm sure pandas could as well. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
time decoding error with "days since" 99836561 | |
129102650 | https://github.com/pydata/xarray/issues/521#issuecomment-129102650 | https://api.github.com/repos/pydata/xarray/issues/521 | MDEyOklzc3VlQ29tbWVudDEyOTEwMjY1MA== | jhamman 2443309 | 2015-08-09T04:03:34Z | 2015-08-09T04:03:34Z | MEMBER | We try to cast all the time variables to a pandas time index. This gives xray the ability to use many of the fast and fancy timeseries tools that pandas has. One consequence of that is that non-standard calendars, such as the "noleap" calendar must have dates inside the valid range of the standard calendars (1678 and 2226). Does that make since? Ideally, numpy and pandas would support custom calendars but they don't so, at this point, we're bound to there limits. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
time decoding error with "days since" 99836561 | |
129059364 | https://github.com/pydata/xarray/issues/521#issuecomment-129059364 | https://api.github.com/repos/pydata/xarray/issues/521 | MDEyOklzc3VlQ29tbWVudDEyOTA1OTM2NA== | jhamman 2443309 | 2015-08-08T22:43:05Z | 2015-08-08T22:43:05Z | MEMBER | @rabernat - Yes - this is all coming from the The work around with xray is to use As an aside, I also work with CESM output and this is a common problem with its netCDF output. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
time decoding error with "days since" 99836561 |
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