issue_comments

Table actions

5 rows where issue = 373574495 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • jhamman · 5 ✖

issue 1

  • xarray 0.11 release · 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
436707493 https://github.com/pydata/xarray/issues/2505#issuecomment-436707493 https://api.github.com/repos/pydata/xarray/issues/2505 MDEyOklzc3VlQ29tbWVudDQzNjcwNzQ5Mw== jhamman 2443309 2018-11-07T17:27:57Z 2018-11-07T17:27:57Z MEMBER

Related and something I could use feedback from @pydata/xarray on: should we drop optional deps from the conda-forge build: https://github.com/conda-forge/xarray-feedstock/pull/37

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 0.11 release 373574495
436686085 https://github.com/pydata/xarray/issues/2505#issuecomment-436686085 https://api.github.com/repos/pydata/xarray/issues/2505 MDEyOklzc3VlQ29tbWVudDQzNjY4NjA4NQ== jhamman 2443309 2018-11-07T16:29:53Z 2018-11-07T16:29:53Z MEMBER

Thanks @shoyer! 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 0.11 release 373574495
436464907 https://github.com/pydata/xarray/issues/2505#issuecomment-436464907 https://api.github.com/repos/pydata/xarray/issues/2505 MDEyOklzc3VlQ29tbWVudDQzNjQ2NDkwNw== jhamman 2443309 2018-11-07T00:57:42Z 2018-11-07T00:57:42Z MEMBER

I'm observing that our checklist seems to be complete. Are we blocked on any outstanding issues?

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 0.11 release 373574495
433098754 https://github.com/pydata/xarray/issues/2505#issuecomment-433098754 https://api.github.com/repos/pydata/xarray/issues/2505 MDEyOklzc3VlQ29tbWVudDQzMzA5ODc1NA== jhamman 2443309 2018-10-25T15:33:53Z 2018-10-25T15:33:53Z MEMBER

Python 2 users know the end is near.

Based on recent experience, I'm not quite as confident here 😄 

{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 1,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 0.11 release 373574495
433093555 https://github.com/pydata/xarray/issues/2505#issuecomment-433093555 https://api.github.com/repos/pydata/xarray/issues/2505 MDEyOklzc3VlQ29tbWVudDQzMzA5MzU1NQ== jhamman 2443309 2018-10-25T15:20:41Z 2018-10-25T15:20:41Z MEMBER

Would it make sense to add a deprecation warning for Python2 users in this release (xref #1876). Chances are, 0.12 will come after Jan-2019 when we're slated to drop Python2 support.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 0.11 release 373574495

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