issue_comments

Table actions

5 rows where issue = 673757961 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date)

user 1

  • dcherian · 5 ✖

issue 1

  • Recreate @gajomi's #2070 to keep attrs when calling astype() · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
676670722 https://github.com/pydata/xarray/pull/4314#issuecomment-676670722 https://api.github.com/repos/pydata/xarray/issues/4314 MDEyOklzc3VlQ29tbWVudDY3NjY3MDcyMg== dcherian 2448579 2020-08-19T20:34:29Z 2020-08-19T20:34:29Z MEMBER

Thanks @dnowacki-usgs 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Recreate @gajomi's #2070 to keep attrs when calling astype() 673757961
670193537 https://github.com/pydata/xarray/pull/4314#issuecomment-670193537 https://api.github.com/repos/pydata/xarray/issues/4314 MDEyOklzc3VlQ29tbWVudDY3MDE5MzUzNw== dcherian 2448579 2020-08-06T21:09:56Z 2020-08-06T21:09:56Z MEMBER

I wonder if we should just let it raise (but xfail our test on sparse < 0.10.0). This is an "imperfect NEP-18 implementation" issue and it isn't feasible to catch all such errors.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Recreate @gajomi's #2070 to keep attrs when calling astype() 673757961
670058108 https://github.com/pydata/xarray/pull/4314#issuecomment-670058108 https://api.github.com/repos/pydata/xarray/issues/4314 MDEyOklzc3VlQ29tbWVudDY3MDA1ODEwOA== dcherian 2448579 2020-08-06T17:08:19Z 2020-08-06T17:08:19Z MEMBER

well that was fixed quickly! Now we need to think of backcompat workarounds.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Recreate @gajomi's #2070 to keep attrs when calling astype() 673757961
670019223 https://github.com/pydata/xarray/pull/4314#issuecomment-670019223 https://api.github.com/repos/pydata/xarray/issues/4314 MDEyOklzc3VlQ29tbWVudDY3MDAxOTIyMw== dcherian 2448579 2020-08-06T16:00:59Z 2020-08-06T16:00:59Z MEMBER

I've opened an issue at sparse. Let's see what the outcome is.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Recreate @gajomi's #2070 to keep attrs when calling astype() 673757961
670014505 https://github.com/pydata/xarray/pull/4314#issuecomment-670014505 https://api.github.com/repos/pydata/xarray/issues/4314 MDEyOklzc3VlQ29tbWVudDY3MDAxNDUwNQ== dcherian 2448579 2020-08-06T15:53:10Z 2020-08-06T15:53:10Z MEMBER

Looks like COO.astype doesn't accept the casting kwarg: https://sparse.pydata.org/en/stable/generated/sparse.COO.astype.html

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Recreate @gajomi's #2070 to keep attrs when calling astype() 673757961

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