issue_comments
2 rows where issue = 775875024 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Slow initilization of dataset.interp · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
752261269 | https://github.com/pydata/xarray/issues/4739#issuecomment-752261269 | https://api.github.com/repos/pydata/xarray/issues/4739 | MDEyOklzc3VlQ29tbWVudDc1MjI2MTI2OQ== | dcherian 2448579 | 2020-12-29T22:19:29Z | 2020-12-29T22:19:29Z | MEMBER |
Now implemented. Runtime has dropped from 5.3s to 2.3s (!) |
{ "total_count": 2, "+1": 0, "-1": 0, "laugh": 0, "hooray": 2, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Slow initilization of dataset.interp 775875024 | |
752210306 | https://github.com/pydata/xarray/issues/4739#issuecomment-752210306 | https://api.github.com/repos/pydata/xarray/issues/4739 | MDEyOklzc3VlQ29tbWVudDc1MjIxMDMwNg== | dcherian 2448579 | 2020-12-29T19:13:27Z | 2020-12-29T19:33:07Z | MEMBER | We don't support lazy index variables yet (#1603) so you can't interpolate to a dask variable.
This may be true. I think we could convert OTOH I found some easier optimizations. See #4740
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Slow initilization of dataset.interp 775875024 |
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