issue_comments
2 rows where issue = 929818771 and user = 5635139 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 868839990 | https://github.com/pydata/xarray/issues/5529#issuecomment-868839990 | https://api.github.com/repos/pydata/xarray/issues/5529 | MDEyOklzc3VlQ29tbWVudDg2ODgzOTk5MA== | max-sixty 5635139 | 2021-06-25T21:21:55Z | 2021-06-25T21:21:55Z | MEMBER | Yes very much so @Illviljan . But weirdly the linked PR is attempting to do that — so maybe this code path doesn't hit that change? Spyder's profiler looks good! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Very poor html repr performance on large multi-indexes 929818771 | |
| 868738004 | https://github.com/pydata/xarray/issues/5529#issuecomment-868738004 | https://api.github.com/repos/pydata/xarray/issues/5529 | MDEyOklzc3VlQ29tbWVudDg2ODczODAwNA== | max-sixty 5635139 | 2021-06-25T17:58:11Z | 2021-06-25T17:58:11Z | MEMBER | Yes, I think it's materializing the multiindex as an array of tuples. Which we definitely shouldn't be doing for reprs. @Illviljan nice profiling view! What is that? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Very poor html repr performance on large multi-indexes 929818771 |
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