issue_comments

Table actions

3 rows where author_association = "CONTRIBUTOR", issue = 589632313 and user = 31126826 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

  • mancellin · 3 ✖

issue 1

  • In-place addition of arrays with the same coords but in a different order · 3 ✖

author_association 1

  • CONTRIBUTOR · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
614146417 https://github.com/pydata/xarray/issues/3910#issuecomment-614146417 https://api.github.com/repos/pydata/xarray/issues/3910 MDEyOklzc3VlQ29tbWVudDYxNDE0NjQxNw== mancellin 31126826 2020-04-15T16:35:46Z 2020-04-15T16:35:46Z CONTRIBUTOR

Well actually, I would be at least as surprised if A += B returned a different result than A = A + B.

So now I understand why this is not supported. I'll submit the PR soon.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   In-place addition of arrays with the same coords but in a different order 589632313
606100412 https://github.com/pydata/xarray/issues/3910#issuecomment-606100412 https://api.github.com/repos/pydata/xarray/issues/3910 MDEyOklzc3VlQ29tbWVudDYwNjEwMDQxMg== mancellin 31126826 2020-03-30T16:22:04Z 2020-03-30T16:22:04Z CONTRIBUTOR

Yes. But the not-in-place addition A+B works fine without conversion to float because it uses basically xr.align(A, B, join='inner'). If the in-place addition did the same, there would be no risk of type conversion. But I guess the in-place version would rather use something like xr.align(A, B, join='left') to guarantee that the shape and index of A does not change. Am I right?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   In-place addition of arrays with the same coords but in a different order 589632313
605847162 https://github.com/pydata/xarray/issues/3910#issuecomment-605847162 https://api.github.com/repos/pydata/xarray/issues/3910 MDEyOklzc3VlQ29tbWVudDYwNTg0NzE2Mg== mancellin 31126826 2020-03-30T08:06:32Z 2020-03-30T08:06:32Z CONTRIBUTOR

I can submit a PR. But the comment cited above is not totally clear to me.

The purpose of the conversion to floats is to have NaNs in case the shapes do not match. So the core of the issue is that A + B might not have the same shape as A, and thus in general A + B cannot replace A in-place. Is that right?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   In-place addition of arrays with the same coords but in a different order 589632313

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