issue_comments

Table actions

1 row where author_association = "NONE" and issue = 435170643 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

issue 1

  • xr.dot result differs from np.dot · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
484956893 https://github.com/pydata/xarray/issues/2907#issuecomment-484956893 https://api.github.com/repos/pydata/xarray/issues/2907 MDEyOklzc3VlQ29tbWVudDQ4NDk1Njg5Mw== lkugler 29361544 2019-04-19T16:59:17Z 2019-04-19T16:59:17Z NONE

Sooo many thanks for this ultrafast response. You're correct. What I didn't know was that the dimensions to multiply have to have the same names. I thought I could sum over different coordinates indicating the names within the dims keyword, but the implementation makes totally sense now. To summarize: Dimensions to sum over have to have the same name and the same ordering of the coordinate values (else f.e. a ValueError: indexes along dimension 'model name' are not equal is raised)

But shouldn't there be an error message if one specifies dimensions to dims that are not in both of the dataarrays?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.dot result differs from np.dot 435170643

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