issue_comments
3 rows where author_association = "MEMBER", issue = 224878728 and user = 6815844 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association, issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
362902669 | https://github.com/pydata/xarray/issues/1388#issuecomment-362902669 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDM2MjkwMjY2OQ== | fujiisoup 6815844 | 2018-02-04T12:20:33Z | 2018-02-04T12:52:29Z | MEMBER | @gajomi Sorry for my late response and thank you for the proposal. But aside from my previous proposal, I was thinking whether such aggregation methods (including Such specific rules may be confusing and bring additional complexity. I think the rule we do not track coordinates after aggregations would be much simpler and easier to understand. If we adopt the above rule, I think the In [4]: da.argmin(dim='x') Out[4]: <xarray.DataArray (y: 3)> array([0, 1, 0]) Coordinates: * y (y) <U1 'a' 'b' 'c' In [3]: da.isel(x=da.argmin(dim='x')) Out[3]: <xarray.DataArray (y: 3)> array([0, 1, 2]) Coordinates: x (y) int64 1 2 1 * y (y) <U1 'a' 'b' 'c' ``` I think your logic would be useful even we do not track the coordinate. I would appreciate any feedback. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
338397633 | https://github.com/pydata/xarray/issues/1388#issuecomment-338397633 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDMzODM5NzYzMw== | fujiisoup 6815844 | 2017-10-21T13:51:04Z | 2017-10-21T13:51:04Z | MEMBER | I am thinking again how (We discussed the name for this new method in #1469 but here I just use For example with a three dimensional array with The above proposal for ii (and iii) is not quite clean, as if it is used as an argument of Any thoughts are welcome. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 | |
309280411 | https://github.com/pydata/xarray/issues/1388#issuecomment-309280411 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDMwOTI4MDQxMQ== | fujiisoup 6815844 | 2017-06-18T14:18:40Z | 2017-06-19T12:56:03Z | MEMBER | I'm working to fix this and I would like to make some design decisions;
Edit:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
argmin / argmax behavior doesn't match documentation 224878728 |
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