issue_comments
2 rows where issue = 793245791 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- nbytes does not return the true size for sparse variables · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 769198581 | https://github.com/pydata/xarray/issues/4842#issuecomment-769198581 | https://api.github.com/repos/pydata/xarray/issues/4842 | MDEyOklzc3VlQ29tbWVudDc2OTE5ODU4MQ== | shoyer 1217238 | 2021-01-28T16:18:16Z | 2021-01-28T16:18:16Z | MEMBER | We should probably be pulling xarray's |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
nbytes does not return the true size for sparse variables 793245791 | |
| 766732368 | https://github.com/pydata/xarray/issues/4842#issuecomment-766732368 | https://api.github.com/repos/pydata/xarray/issues/4842 | MDEyOklzc3VlQ29tbWVudDc2NjczMjM2OA== | benbovy 4160723 | 2021-01-25T10:56:05Z | 2021-01-25T10:56:05Z | MEMBER | I guess it could be possible to do a typecheck for this case. It's tricky to have a smart |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
nbytes does not return the true size for sparse variables 793245791 |
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 2