issue_comments

Table actions

1 row where issue = 657230088 and user = 199813 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

  • tacaswell · 1 ✖

issue 1

  • failing upstream-dev CI: matplotlib · 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
663030222 https://github.com/pydata/xarray/issues/4226#issuecomment-663030222 https://api.github.com/repos/pydata/xarray/issues/4226 MDEyOklzc3VlQ29tbWVudDY2MzAzMDIyMg== tacaswell 199813 2020-07-23T14:11:33Z 2020-07-23T14:11:33Z NONE

That changes was definitely intentional in BoundaryNorm, but we thought that we were giving a clear error in a case where you used to get a divide by 0 error.

I think we used to implicitly change 1 boundary into a degenerate 2 boundary, I can see the argument that we should be more forgiving, but in boundry norm I'm not sure what that would mean (internally we are going to make every value to either over or under. If you want to support this at the xarray level you should do the [4] -> [4, 4] conversion which will work with all version of Matplotlib.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   failing upstream-dev CI: matplotlib 657230088

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