issue_comments
2 rows where issue = 1050937380 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Typing of dim in concat.py does not include Hashable · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1129296328 | https://github.com/pydata/xarray/issues/5975#issuecomment-1129296328 | https://api.github.com/repos/pydata/xarray/issues/5975 | IC_kwDOAMm_X85DT7HI | headtr1ck 43316012 | 2022-05-17T20:39:03Z | 2022-05-17T20:39:03Z | COLLABORATOR | Should support Hashable now. |
{
"total_count": 2,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 2,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Typing of dim in concat.py does not include Hashable 1050937380 | |
| 966736703 | https://github.com/pydata/xarray/issues/5975#issuecomment-966736703 | https://api.github.com/repos/pydata/xarray/issues/5975 | IC_kwDOAMm_X845nzs_ | max-sixty 5635139 | 2021-11-12T01:06:48Z | 2021-11-12T01:06:48Z | MEMBER | I'd be open to changing this, though I'm not sure everything supports non-str dims. IIRC there is an issue around using tuples, for example. Does anyone have a more informed view? TBC, we should support non-dim variable names in datasets already. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Typing of dim in concat.py does not include Hashable 1050937380 |
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