issue_comments

Table actions

3 rows where issue = 1417378270 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 2

issue 1

  • Example using Coarsen.construct to split map into regions · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1287210738 https://github.com/pydata/xarray/pull/7192#issuecomment-1287210738 https://api.github.com/repos/pydata/xarray/issues/7192 IC_kwDOAMm_X85MuUby dcherian 2448579 2022-10-21T16:49:16Z 2022-10-21T16:49:16Z MEMBER

/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7192/doc/whats-new.rst:2999: WARNING: undefined label: comput.coarsen /home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7192/doc/whats-new.rst:3054: WARNING: undefined label: comput.coarsen

We fail in warnings in RTD

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Example using Coarsen.construct to split map into regions 1417378270
1287194617 https://github.com/pydata/xarray/pull/7192#issuecomment-1287194617 https://api.github.com/repos/pydata/xarray/issues/7192 IC_kwDOAMm_X85MuQf5 TomNicholas 35968931 2022-10-21T16:34:44Z 2022-10-21T16:35:04Z MEMBER

LGTM as long as it renders nicely.

It renders nicely locally, but any idea why the RTD build fails so opaquely?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Example using Coarsen.construct to split map into regions 1417378270
1286231676 https://github.com/pydata/xarray/pull/7192#issuecomment-1286231676 https://api.github.com/repos/pydata/xarray/issues/7192 IC_kwDOAMm_X85MqlZ8 dcherian 2448579 2022-10-20T22:32:56Z 2022-10-20T22:32:56Z MEMBER

Unsure whether it should instead live in the page on reshaping and reorganising data though, as it is essentially a reshape operation.

This would be good IMO

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Example using Coarsen.construct to split map into regions 1417378270

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