issue_comments
3 rows where issue = 956103236 and user = 306380 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Duck array compatibility meeting · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
925015359 | https://github.com/pydata/xarray/issues/5648#issuecomment-925015359 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X843Ip0_ | mrocklin 306380 | 2021-09-22T15:01:06Z | 2021-09-22T15:01:06Z | MEMBER | It looks like there are some other Dask folks participating. I'll step back and let them take over on our end. On Wed, Sep 22, 2021 at 9:53 AM Hameer Abbasi @.***> wrote:
|
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Duck array compatibility meeting 956103236 | |
924104833 | https://github.com/pydata/xarray/issues/5648#issuecomment-924104833 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X843FLiB | mrocklin 306380 | 2021-09-21T15:32:58Z | 2021-09-21T15:32:58Z | MEMBER | Surprisingly I happen to be free tomorrow at exactly that time. I've blocked it off. If you want to send a calendar invite to mrocklin at coiled that would be welcome. On Tue, Sep 21, 2021 at 10:27 AM Tom Nicholas @.***> wrote:
|
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 0 } |
Duck array compatibility meeting 956103236 | |
889468552 | https://github.com/pydata/xarray/issues/5648#issuecomment-889468552 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X841BDaI | mrocklin 306380 | 2021-07-29T21:21:38Z | 2021-07-29T21:21:38Z | MEMBER | I would be happy to attend and look forward to what I'm sure will be a vigorous discussion :) Thank you for providing convenient links to reading materials ahead of time. As a warning, my responsiveness to github comments these days is not what it used to be. If I miss something here then please forgive me. |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 0 } |
Duck array compatibility meeting 956103236 |
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