issue_comments
4 rows where author_association = "MEMBER" and issue = 100055216 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Option for closing files with scipy backend · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
228412831 | https://github.com/pydata/xarray/pull/524#issuecomment-228412831 | https://api.github.com/repos/pydata/xarray/issues/524 | MDEyOklzc3VlQ29tbWVudDIyODQxMjgzMQ== | shoyer 1217238 | 2016-06-24T17:45:07Z | 2016-06-24T17:45:07Z | MEMBER | Something like this is still worth exploring (the LRU cache), but this isn't quite the right solution. So I'm closing this PR, just to clean up the list of outstanding PRs :). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option for closing files with scipy backend 100055216 | |
205354820 | https://github.com/pydata/xarray/pull/524#issuecomment-205354820 | https://api.github.com/repos/pydata/xarray/issues/524 | MDEyOklzc3VlQ29tbWVudDIwNTM1NDgyMA== | rabernat 1197350 | 2016-04-04T15:37:16Z | 2016-04-04T15:37:16Z | MEMBER | Really? I figured this was a doomed concept. @pwolfram it looks like you are doing the hard work that I did not have the time or expertise for. This will pay off big time once the distributed backend is working. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option for closing files with scipy backend 100055216 | |
147857068 | https://github.com/pydata/xarray/pull/524#issuecomment-147857068 | https://api.github.com/repos/pydata/xarray/issues/524 | MDEyOklzc3VlQ29tbWVudDE0Nzg1NzA2OA== | rabernat 1197350 | 2015-10-13T21:19:14Z | 2015-10-13T21:19:14Z | MEMBER | I considered this more of a proof of concept than a serious PR. It was incredibly slow, but it circumvented the ulimit restriction. Probably not the best solution. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option for closing files with scipy backend 100055216 | |
147810879 | https://github.com/pydata/xarray/pull/524#issuecomment-147810879 | https://api.github.com/repos/pydata/xarray/issues/524 | MDEyOklzc3VlQ29tbWVudDE0NzgxMDg3OQ== | jhamman 2443309 | 2015-10-13T18:49:25Z | 2015-10-13T18:49:25Z | MEMBER | @shoyer and @rabernat - what do we want to do with this? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option for closing files with scipy backend 100055216 |
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 3