issue_comments

Table actions

2 rows where issue = 138086327 and user = 950575 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

  • ocefpaf · 2 ✖

issue 1

  • dont infer interval breaks in pcolormesh when ax is a cartopy axis · 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
191840829 https://github.com/pydata/xarray/pull/782#issuecomment-191840829 https://api.github.com/repos/pydata/xarray/issues/782 MDEyOklzc3VlQ29tbWVudDE5MTg0MDgyOQ== ocefpaf 950575 2016-03-03T16:32:20Z 2016-03-03T16:33:54Z CONTRIBUTOR

What if there are bounds in the file and the data is regularly spaced? I consider the current behavior a guess, and guessing should be an active user choice, not the automatic behavior. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   dont infer interval breaks in pcolormesh when ax is a cartopy axis 138086327
191607244 https://github.com/pydata/xarray/pull/782#issuecomment-191607244 https://api.github.com/repos/pydata/xarray/issues/782 MDEyOklzc3VlQ29tbWVudDE5MTYwNzI0NA== ocefpaf 950575 2016-03-03T06:35:02Z 2016-03-03T06:35:02Z CONTRIBUTOR

Bare in mind that some netCDF4 files do have the bounds data and those should be used as "breaks" when available.

BTW I'd rather not have the _infer_interval_breaks at all, not sure if assuming linear at the mid points are generic enough.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   dont infer interval breaks in pcolormesh when ax is a cartopy axis 138086327

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