issue_comments

Table actions

3 rows where author_association = "MEMBER" and issue = 685825824 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • wrong chunk sizes in html repr with nonuniform chunks · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
704864577 https://github.com/pydata/xarray/issues/4376#issuecomment-704864577 https://api.github.com/repos/pydata/xarray/issues/4376 MDEyOklzc3VlQ29tbWVudDcwNDg2NDU3Nw== keewis 14808389 2020-10-07T11:11:22Z 2020-10-07T11:11:22Z MEMBER

for that to work I guess we first have to improve the documentation on _repr_inline_ (see https://github.com/pydata/xarray/pull/4248#discussion_r466546100)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   wrong chunk sizes in html repr with nonuniform chunks 685825824
704612055 https://github.com/pydata/xarray/issues/4376#issuecomment-704612055 https://api.github.com/repos/pydata/xarray/issues/4376 MDEyOklzc3VlQ29tbWVudDcwNDYxMjA1NQ== dcherian 2448579 2020-10-06T23:50:53Z 2020-10-06T23:50:53Z MEMBER

I agree. We should outsource this to dask

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   wrong chunk sizes in html repr with nonuniform chunks 685825824
680296332 https://github.com/pydata/xarray/issues/4376#issuecomment-680296332 https://api.github.com/repos/pydata/xarray/issues/4376 MDEyOklzc3VlQ29tbWVudDY4MDI5NjMzMg== keewis 14808389 2020-08-25T22:15:11Z 2020-08-25T22:15:11Z MEMBER

that's because we're actively picking the first element of each chunk: https://github.com/pydata/xarray/blob/9c85dd5f792805bea319f01f08ee51b83bde0f3b/xarray/core/formatting.py#L233

Maybe it's time to finalize _repr_inline_ and try to get dask to implement it? Or, if that doesn't work, we could also monkeypatch it onto dask arrays, similar to what pint-xarray is doing with pint quantities.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   wrong chunk sizes in html repr with nonuniform chunks 685825824

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