issue_comments
4 rows where issue = 563762277 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- ArviZ Dev Xarray Dev Get Together? · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
605154030 | https://github.com/pydata/xarray/issues/3765#issuecomment-605154030 | https://api.github.com/repos/pydata/xarray/issues/3765 | MDEyOklzc3VlQ29tbWVudDYwNTE1NDAzMA== | max-sixty 5635139 | 2020-03-27T17:50:09Z | 2020-03-27T17:50:09Z | MEMBER | Thanks @canyon289 ! Great to meet you all and I thought really helpful to talk through the cases with everyone. Indeed: having some cases to go over made the time much more productive. I look forward to keeping the thread going... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ArviZ Dev Xarray Dev Get Together? 563762277 | |
600330366 | https://github.com/pydata/xarray/issues/3765#issuecomment-600330366 | https://api.github.com/repos/pydata/xarray/issues/3765 | MDEyOklzc3VlQ29tbWVudDYwMDMzMDM2Ng== | max-sixty 5635139 | 2020-03-17T22:27:07Z | 2020-03-17T22:27:07Z | MEMBER | To the extent we can do later in the day, that would be easier for those on US west coast time... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ArviZ Dev Xarray Dev Get Together? 563762277 | |
585303992 | https://github.com/pydata/xarray/issues/3765#issuecomment-585303992 | https://api.github.com/repos/pydata/xarray/issues/3765 | MDEyOklzc3VlQ29tbWVudDU4NTMwMzk5Mg== | max-sixty 5635139 | 2020-02-12T16:53:24Z | 2020-02-12T16:53:24Z | MEMBER | @TomNicholas we probably do need to be better on SO. I've tried to do more there now I'm not contributing as much. I've found the questions are sometimes difficult to engage with as they're dependent on an external dataset (i.e. much lower quality than those here). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ArviZ Dev Xarray Dev Get Together? 563762277 | |
585224201 | https://github.com/pydata/xarray/issues/3765#issuecomment-585224201 | https://api.github.com/repos/pydata/xarray/issues/3765 | MDEyOklzc3VlQ29tbWVudDU4NTIyNDIwMQ== | max-sixty 5635139 | 2020-02-12T14:14:03Z | 2020-02-12T14:14:03Z | MEMBER | I'm keen! Given work schedules, it may be easiest to do at a conference. We could also do a remote meeting. The repo is ideal prep. The current two examples are good general questions about using Xarray even beyond ArviZ. And more generally, I'm happy that ArviZ has built on top on xarray, and we're keen to support that! |
{ "total_count": 3, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 2, "rocket": 0, "eyes": 0 } |
ArviZ Dev Xarray Dev Get Together? 563762277 |
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