issue_comments

Table actions

1 row where issue = 1424732975 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • keewis · 1 ✖

issue 1

  • Fix coordinate attr handling in `xr.where(..., keep_attrs=True)` · 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
1306330043 https://github.com/pydata/xarray/pull/7229#issuecomment-1306330043 https://api.github.com/repos/pydata/xarray/issues/7229 IC_kwDOAMm_X85N3QO7 keewis 14808389 2022-11-07T22:48:01Z 2022-11-07T22:48:01Z MEMBER

this seems like a serious edge case

That particular example might be rare, but [DataArray, scalar, DataArray] will select the attrs of y, which is just as bad, and arguably more common (though for units this will not really matter, since x and y should have the same units, anyways).

In any case, I will try to push this forward so this can be fixed as soon as possible.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix coordinate attr handling in `xr.where(..., keep_attrs=True)` 1424732975

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