issue_comments

Table actions

1 row where issue = 340733448 and user = 8168220 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

  • javierdvalle · 1 ✖

issue 1

  • Exact alignment should allow missing dimension coordinates · 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
861358903 https://github.com/pydata/xarray/issues/2283#issuecomment-861358903 https://api.github.com/repos/pydata/xarray/issues/2283 MDEyOklzc3VlQ29tbWVudDg2MTM1ODkwMw== javierdvalle 8168220 2021-06-15T09:52:29Z 2021-06-15T09:52:29Z NONE

I encountered this error while using dot.

I agree with @shoyer, raising an error here is not the expected behaviour, it should automatically handle the join: instead of raising an error, compute the dot product just for the coordinates existing in both arrays, and discard the rest ("inner" join).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Exact alignment should allow missing dimension coordinates 340733448

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