issue_comments
where author_association = "MEMBER", issue = 777153550 and user = 1217238 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 753416850 | https://github.com/pydata/xarray/pull/4746#issuecomment-753416850 | https://api.github.com/repos/pydata/xarray/issues/4746 | MDEyOklzc3VlQ29tbWVudDc1MzQxNjg1MA== | shoyer 1217238 | 2021-01-02T02:00:19Z | 2021-01-02T02:00:19Z | MEMBER | @keewis any thoughts on the pint issue? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Faster unstacking 777153550 | |
| 753282125 | https://github.com/pydata/xarray/pull/4746#issuecomment-753282125 | https://api.github.com/repos/pydata/xarray/issues/4746 | MDEyOklzc3VlQ29tbWVudDc1MzI4MjEyNQ== | shoyer 1217238 | 2021-01-01T07:52:14Z | 2021-01-01T07:52:14Z | MEMBER | Very nice! I think we solve the issue with sparse by using The bigger challenge that I'm concerned about here are dask arrays, which don't support array assignment like this at all (https://github.com/dask/dask/issues/2000). We will probably need to keep around the slower option for dask, at least for now. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Faster unstacking 777153550 |
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