issue_comments
8 rows where issue = 195050684 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Generated Dask graph is huge - performance issue? · 8 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
274605239 | https://github.com/pydata/xarray/issues/1161#issuecomment-274605239 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI3NDYwNTIzOQ== | shoyer 1217238 | 2017-01-23T20:21:14Z | 2017-01-23T20:21:14Z | MEMBER | Fixed by #1162 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266598007 | https://github.com/pydata/xarray/issues/1161#issuecomment-266598007 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjU5ODAwNw== | mangecoeur 743508 | 2016-12-13T00:29:16Z | 2016-12-13T00:29:16Z | CONTRIBUTOR | Seems to run a lot faster for me too... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266596464 | https://github.com/pydata/xarray/issues/1161#issuecomment-266596464 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjU5NjQ2NA== | mangecoeur 743508 | 2016-12-13T00:20:12Z | 2016-12-13T00:20:12Z | CONTRIBUTOR | Done with PR #1162 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266588337 | https://github.com/pydata/xarray/issues/1161#issuecomment-266588337 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjU4ODMzNw== | shoyer 1217238 | 2016-12-12T23:34:41Z | 2016-12-12T23:34:41Z | MEMBER |
Yes, please do -- that's much easier to read and comment on than what you have here. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266587849 | https://github.com/pydata/xarray/issues/1161#issuecomment-266587849 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjU4Nzg0OQ== | mangecoeur 743508 | 2016-12-12T23:32:19Z | 2016-12-12T23:33:03Z | CONTRIBUTOR | Thanks, I've been looking around and I think i'm getting close, however i'm not sure the best way to turn the array slice i get from vindex into a DataArray variable. I'm thinking I might but together a draft PR for comments. This is what i have so far: ```python def isel_points(self, dim='points', **indexers): """Returns a new dataset with each array indexed pointwise along the specified dimension(s).
return concat([self.isel(**d) for d in[dict(zip(keys, inds)) for inds inzip(*[v for k, v in indexers])]],dim=dim, coords=coords, data_vars=data_vars)``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266526859 | https://github.com/pydata/xarray/issues/1161#issuecomment-266526859 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjUyNjg1OQ== | shoyer 1217238 | 2016-12-12T19:27:28Z | 2016-12-12T19:27:28Z | MEMBER | nothing about the logic is dask specific currently |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266519121 | https://github.com/pydata/xarray/issues/1161#issuecomment-266519121 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjUxOTEyMQ== | mangecoeur 743508 | 2016-12-12T18:59:15Z | 2016-12-12T18:59:15Z | CONTRIBUTOR | Ok I will have a look, where is this implemented (I always seem to have trouble pinpointing the dask-specific bits in the codebase :S ) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 | |
266517317 | https://github.com/pydata/xarray/issues/1161#issuecomment-266517317 | https://api.github.com/repos/pydata/xarray/issues/1161 | MDEyOklzc3VlQ29tbWVudDI2NjUxNzMxNw== | shoyer 1217238 | 2016-12-12T18:52:35Z | 2016-12-12T18:52:35Z | MEMBER | Indeed, Could be worth experimenting with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Generated Dask graph is huge - performance issue? 195050684 |
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 2