issue_comments
2 rows where author_association = "MEMBER" and issue = 1583216781 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- contiguous time axis · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1449074103 | https://github.com/pydata/xarray/issues/7525#issuecomment-1449074103 | https://api.github.com/repos/pydata/xarray/issues/7525 | IC_kwDOAMm_X85WXx23 | dcherian 2448579 | 2023-02-28T23:17:08Z | 2023-02-28T23:17:08Z | MEMBER | Thanks @dopplershift and @ethanrd . It seems like it's interpreting the absence of an attribute (!). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
contiguous time axis 1583216781 | |
1447570204 | https://github.com/pydata/xarray/issues/7525#issuecomment-1447570204 | https://api.github.com/repos/pydata/xarray/issues/7525 | IC_kwDOAMm_X85WSCsc | dcherian 2448579 | 2023-02-28T04:48:23Z | 2023-02-28T04:48:23Z | MEMBER | Presumably there is some attribute that netcdf-Java is interpreting. It's not clear to me what that is. Perhaps @dopplershift has an idea. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
contiguous time axis 1583216781 |
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