issue_comments

Table actions

1 row where issue = 1608352581 and user = 39069044 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

  • slevang · 1 ✖

issue 1

  • xr.where loses attributes despite 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
1454968267 https://github.com/pydata/xarray/issues/7581#issuecomment-1454968267 https://api.github.com/repos/pydata/xarray/issues/7581 IC_kwDOAMm_X85WuQ3L slevang 39069044 2023-03-05T02:45:42Z 2023-03-05T02:45:42Z CONTRIBUTOR

xr.where(cond, x, y, keep_attrs=True) unambiguously takes the attributes of x as described in the docs, even if x is a scalar and has no attributes. This can be inconvenient at times but is intentional for consistency. You can invert the condition as you suggest, or better yet use DataArray.where/Dataset.where to ensure you are getting the attrs you expect.

In what case would a!=0 not mirror a==0?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.where loses attributes despite keep_attrs=True 1608352581

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