issue_comments
4 rows where author_association = "MEMBER", issue = 713834297 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Allow skipna in .dot() · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
708088129 | https://github.com/pydata/xarray/issues/4482#issuecomment-708088129 | https://api.github.com/repos/pydata/xarray/issues/4482 | MDEyOklzc3VlQ29tbWVudDcwODA4ODEyOQ== | max-sixty 5635139 | 2020-10-14T00:50:40Z | 2020-10-14T00:50:40Z | MEMBER | Right — that makes sense now. Given that So I think there's a spectrum of implementations of The second would be required for @heerad 's case above |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow skipna in .dot() 713834297 | |
706442785 | https://github.com/pydata/xarray/issues/4482#issuecomment-706442785 | https://api.github.com/repos/pydata/xarray/issues/4482 | MDEyOklzc3VlQ29tbWVudDcwNjQ0Mjc4NQ== | max-sixty 5635139 | 2020-10-09T23:29:23Z | 2020-10-09T23:29:23Z | MEMBER | Maybe on very small arrays it's quicker to do a product than a copy? As the array scales, it's surely not — dot product is O(n^3) or similar. I would be interested to see a repro... |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow skipna in .dot() 713834297 | |
704634447 | https://github.com/pydata/xarray/issues/4482#issuecomment-704634447 | https://api.github.com/repos/pydata/xarray/issues/4482 | MDEyOklzc3VlQ29tbWVudDcwNDYzNDQ0Nw== | max-sixty 5635139 | 2020-10-07T01:12:09Z | 2020-10-07T01:12:09Z | MEMBER | Any idea why For some functions where |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow skipna in .dot() 713834297 | |
702937094 | https://github.com/pydata/xarray/issues/4482#issuecomment-702937094 | https://api.github.com/repos/pydata/xarray/issues/4482 | MDEyOklzc3VlQ29tbWVudDcwMjkzNzA5NA== | max-sixty 5635139 | 2020-10-02T20:13:37Z | 2020-10-02T20:13:37Z | MEMBER | I agree this would be a welcome option. As a workaround, you could fillna with zero? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow skipna in .dot() 713834297 |
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