home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER", issue = 138045063 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

These facets timed out: author_association, issue

user 1

  • shoyer · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
256964206 https://github.com/pydata/xarray/issues/781#issuecomment-256964206 https://api.github.com/repos/pydata/xarray/issues/781 MDEyOklzc3VlQ29tbWVudDI1Njk2NDIwNg== shoyer 1217238 2016-10-28T16:20:44Z 2016-10-28T16:20:44Z MEMBER

I think a keyword argument is a pretty solid way to handle this. Detecting uniform coordinates specified with floating point numbers is pretty error prone.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Don't infer x/y coordinates interval breaks for cartopy plot axes 138045063
191597245 https://github.com/pydata/xarray/issues/781#issuecomment-191597245 https://api.github.com/repos/pydata/xarray/issues/781 MDEyOklzc3VlQ29tbWVudDE5MTU5NzI0NQ== shoyer 1217238 2016-03-03T06:08:46Z 2016-03-03T06:08:46Z MEMBER

OK, that seem pretty compelling to me. You do lose one row of data across the top of the image, but that's better than the artifact.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Don't infer x/y coordinates interval breaks for cartopy plot axes 138045063
191546524 https://github.com/pydata/xarray/issues/781#issuecomment-191546524 https://api.github.com/repos/pydata/xarray/issues/781 MDEyOklzc3VlQ29tbWVudDE5MTU0NjUyNA== shoyer 1217238 2016-03-03T02:21:30Z 2016-03-03T02:21:30Z MEMBER

Inferring x/y coordinate breaks solves the puzzle of losing the last row and column of data when plotting with pcolormesh.

Are your coordinates very unevenly spaced? I'm curious what goes wrong here -- it's nice to plot all the data if possible.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Don't infer x/y coordinates interval breaks for cartopy plot axes 138045063

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 1592.778ms · About: xarray-datasette