issue_comments
5 rows where author_association = "MEMBER" and issue = 140264913 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- ENH: Don't infer pcolormesh interval breaks for unevenly spaced coordiantes · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
458314129 | https://github.com/pydata/xarray/issues/792#issuecomment-458314129 | https://api.github.com/repos/pydata/xarray/issues/792 | MDEyOklzc3VlQ29tbWVudDQ1ODMxNDEyOQ== | fmaussion 10050469 | 2019-01-28T21:46:18Z | 2019-01-28T21:46:18Z | MEMBER | especially because there is not robust logic as to how to check for coordinates being evenly spaced. I remember this topic has been discussed somewhere already, but I don't remember where. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Don't infer pcolormesh interval breaks for unevenly spaced coordiantes 140264913 | |
458311494 | https://github.com/pydata/xarray/issues/792#issuecomment-458311494 | https://api.github.com/repos/pydata/xarray/issues/792 | MDEyOklzc3VlQ29tbWVudDQ1ODMxMTQ5NA== | fmaussion 10050469 | 2019-01-28T21:37:53Z | 2019-01-28T21:37:53Z | MEMBER | yes, also the current solution isn't too bad as well. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Don't infer pcolormesh interval breaks for unevenly spaced coordiantes 140264913 | |
458280999 | https://github.com/pydata/xarray/issues/792#issuecomment-458280999 | https://api.github.com/repos/pydata/xarray/issues/792 | MDEyOklzc3VlQ29tbWVudDQ1ODI4MDk5OQ== | dcherian 2448579 | 2019-01-28T20:05:04Z | 2019-01-28T20:05:04Z | MEMBER | still relevant |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Don't infer pcolormesh interval breaks for unevenly spaced coordiantes 140264913 | |
195542223 | https://github.com/pydata/xarray/issues/792#issuecomment-195542223 | https://api.github.com/repos/pydata/xarray/issues/792 | MDEyOklzc3VlQ29tbWVudDE5NTU0MjIyMw== | jhamman 2443309 | 2016-03-11T20:40:03Z | 2016-03-11T20:40:03Z | MEMBER | I agree, 1 seems to be the easiest. @clarkfitzg P.S. I think we're in the same boat, new baby and I'm just a few months from my defense. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Don't infer pcolormesh interval breaks for unevenly spaced coordiantes 140264913 | |
195536929 | https://github.com/pydata/xarray/issues/792#issuecomment-195536929 | https://api.github.com/repos/pydata/xarray/issues/792 | MDEyOklzc3VlQ29tbWVudDE5NTUzNjkyOQ== | clarkfitzg 5356122 | 2016-03-11T20:28:26Z | 2016-03-11T20:28:26Z | MEMBER | Thanks for keeping me in the loop- hopefully next month I can participate. New baby and Phd quals => no time now 1 appears to be the simpler option off the top of my head. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Don't infer pcolormesh interval breaks for unevenly spaced coordiantes 140264913 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 4