issue_comments
3 rows where issue = 287569331 and user = 10050469 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- fix rasterio chunking with s3 datasets · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
360072572 | https://github.com/pydata/xarray/pull/1817#issuecomment-360072572 | https://api.github.com/repos/pydata/xarray/issues/1817 | MDEyOklzc3VlQ29tbWVudDM2MDA3MjU3Mg== | fmaussion 10050469 | 2018-01-24T09:33:07Z | 2018-01-24T09:33:07Z | MEMBER | @rabernat no problem, will go back the rasterio tests soon |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fix rasterio chunking with s3 datasets 287569331 | |
359827458 | https://github.com/pydata/xarray/pull/1817#issuecomment-359827458 | https://api.github.com/repos/pydata/xarray/issues/1817 | MDEyOklzc3VlQ29tbWVudDM1OTgyNzQ1OA== | fmaussion 10050469 | 2018-01-23T15:32:15Z | 2018-01-23T15:32:15Z | MEMBER | test_nodata and test_nodata_missing are tests which were added in https://github.com/pydata/xarray/pull/1740, they shouldn't be deleted by your PR. It's fine if you don't refactorize them (I'll need to have a look at all the tests anyway once all conflicting PRs are merged, see https://github.com/pydata/xarray/issues/1843) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fix rasterio chunking with s3 datasets 287569331 | |
357457030 | https://github.com/pydata/xarray/pull/1817#issuecomment-357457030 | https://api.github.com/repos/pydata/xarray/issues/1817 | MDEyOklzc3VlQ29tbWVudDM1NzQ1NzAzMA== | fmaussion 10050469 | 2018-01-13T18:44:37Z | 2018-01-13T18:44:37Z | MEMBER | https://github.com/pydata/xarray/pull/1740 is OK since the tests are still missing. My PR is a bit more problematic, but I can handle it. I would favor pushing yours forward now and I'll rebase my PR on top of it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fix rasterio chunking with s3 datasets 287569331 |
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 1