issue_comments

Table actions

5 rows where author_association = "MEMBER", issue = 492866552 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • max-sixty · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
554503077 https://github.com/pydata/xarray/pull/3302#issuecomment-554503077 https://api.github.com/repos/pydata/xarray/issues/3302 MDEyOklzc3VlQ29tbWVudDU1NDUwMzA3Nw== max-sixty 5635139 2019-11-15T19:49:12Z 2019-11-15T19:49:12Z MEMBER

Great, thanks @dcherian !

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interpolate_na: Add max_gap support. 492866552
531843795 https://github.com/pydata/xarray/pull/3302#issuecomment-531843795 https://api.github.com/repos/pydata/xarray/issues/3302 MDEyOklzc3VlQ29tbWVudDUzMTg0Mzc5NQ== max-sixty 5635139 2019-09-16T16:02:57Z 2019-09-16T16:02:57Z MEMBER

IIUC, and please correct me if I'm wrong, the pandas version counts points rather than the distance between locations. Ideally we'd be able to do both, but even if we can only have one working correctly, that would be v good

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interpolate_na: Add max_gap support. 492866552
531286079 https://github.com/pydata/xarray/pull/3302#issuecomment-531286079 https://api.github.com/repos/pydata/xarray/issues/3302 MDEyOklzc3VlQ29tbWVudDUzMTI4NjA3OQ== max-sixty 5635139 2019-09-13T15:36:08Z 2019-09-13T15:36:08Z MEMBER

I think using locations rather than counts would be great, but harder and doesn't have to be part of this PR.

In the example above, it looks like 1 is aligned with 6 and 4 with 10, so the gap in locations along the y dimension would be 4?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interpolate_na: Add max_gap support. 492866552
531036675 https://github.com/pydata/xarray/pull/3302#issuecomment-531036675 https://api.github.com/repos/pydata/xarray/issues/3302 MDEyOklzc3VlQ29tbWVudDUzMTAzNjY3NQ== max-sixty 5635139 2019-09-12T22:52:24Z 2019-09-12T22:52:24Z MEMBER

As per the pandas issue, sounds like max_gap is consensus

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interpolate_na: Add max_gap support. 492866552
530899448 https://github.com/pydata/xarray/pull/3302#issuecomment-530899448 https://api.github.com/repos/pydata/xarray/issues/3302 MDEyOklzc3VlQ29tbWVudDUzMDg5OTQ0OA== max-sixty 5635139 2019-09-12T16:17:46Z 2019-09-12T16:17:46Z MEMBER

OK it looks like that PR is alive again, so maybe it's good to keep the same kwarg?

Ah, agree we should align. I'm really not keen on that name but yes on balance; unless they're open to changing

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interpolate_na: Add max_gap support. 492866552

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);