home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 138086327 and user = 1217238 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • shoyer · 2 ✖

issue 1

  • dont infer interval breaks in pcolormesh when ax is a cartopy axis · 2 ✖

author_association 1

  • MEMBER 2
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
195492662 https://github.com/pydata/xarray/pull/782#issuecomment-195492662 https://api.github.com/repos/pydata/xarray/issues/782 MDEyOklzc3VlQ29tbWVudDE5NTQ5MjY2Mg== shoyer 1217238 2016-03-11T18:40:56Z 2016-03-11T18:40:56Z MEMBER

Works for me

On Fri, Mar 11, 2016 at 10:40 AM, Joe Hamman notifications@github.com wrote:

So do we want to remove _infer_interval_breaks all together in this PR? I'm leaning toward merging this as is and following up with another PR to handle the unevenly spaced coordinates in the future.

— Reply to this email directly or view it on GitHub https://github.com/pydata/xarray/pull/782#issuecomment-195492398.

{
    "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
195455648 https://github.com/pydata/xarray/pull/782#issuecomment-195455648 https://api.github.com/repos/pydata/xarray/issues/782 MDEyOklzc3VlQ29tbWVudDE5NTQ1NTY0OA== shoyer 1217238 2016-03-11T17:03:41Z 2016-03-11T17:03:41Z MEMBER

This PR looks good to me.

Regarding the larger issue of not inferring bounds, I guess I would be on board with that change, too. The original idea was to make pcolormesh and imshow consistent (other than the underlying plotting engine) and to always plot that last row/column of data, but maybe it's better to force users to be explicit. At the very least, it is clearly a bad idea to adjust bounds if they are not equally spaced (but I agree that guessing is bad default 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

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]);
Powered by Datasette · Queries took 1540.826ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows