issue_comments

Table actions

1 row where issue = 1116080396 and user = 11994217 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • dionhaefner · 1 ✖

issue 1

  • MNT: prepare h5netcdf backend for (coming) change in dimension handling · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1023380783 https://github.com/pydata/xarray/pull/6200#issuecomment-1023380783 https://api.github.com/repos/pydata/xarray/issues/6200 IC_kwDOAMm_X848_40v dionhaefner 11994217 2022-01-27T16:08:50Z 2022-01-27T16:08:50Z CONTRIBUTOR

@dionhaefner

Could you please have a look at the chunksizes FutureWarnings (eg. here https://github.com/pydata/xarray/runs/4965336696?check_suite_focus=true#step:8:344).

Are the chunksizes via h5py and via h5netcdf heuristics correct?

Let's take this in https://github.com/h5netcdf/h5netcdf/issues/149.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   MNT: prepare h5netcdf backend for (coming) change in dimension handling 1116080396

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