issue_comments

Table actions

2 rows where issue = 354923742 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • Test equality of DataArrays up to transposition · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
427812992 https://github.com/pydata/xarray/issues/2388#issuecomment-427812992 https://api.github.com/repos/pydata/xarray/issues/2388 MDEyOklzc3VlQ29tbWVudDQyNzgxMjk5Mg== TomNicholas 35968931 2018-10-08T12:25:46Z 2018-10-08T12:25:46Z MEMBER

I did not realise that method existed, and unless you think a keyword argument is needed then I'm happy to just use that method!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Test equality of DataArrays up to transposition 354923742
416785448 https://github.com/pydata/xarray/issues/2388#issuecomment-416785448 https://api.github.com/repos/pydata/xarray/issues/2388 MDEyOklzc3VlQ29tbWVudDQxNjc4NTQ0OA== shoyer 1217238 2018-08-29T00:41:14Z 2018-08-29T00:41:36Z MEMBER

We have a broadcast_equals() method on DataArray and Dataset that broadcasts the arguments first and could be used for this purpose, e.g., assert da1.broadcast_equals(da2)

I'm slightly reluctant to add a new testing function specifically for this, because they we have to explain the difference between "equivalent" and "equal". Maybe some new keyword arguments for assert_equal would be appropriate? e.g., allow_transpose=True and/or broadcast=True?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Test equality of DataArrays up to transposition 354923742

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