issue_comments
2 rows where issue = 788398518 and user = 226037 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Allow fsspec URLs in open_(mf)dataset · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 764610726 | https://github.com/pydata/xarray/pull/4823#issuecomment-764610726 | https://api.github.com/repos/pydata/xarray/issues/4823 | MDEyOklzc3VlQ29tbWVudDc2NDYxMDcyNg== | alexamici 226037 | 2021-01-21T12:29:32Z | 2021-01-21T12:29:32Z | MEMBER | @martindurant with respect to the backend API (old and new) looks good to me. I'm don't know |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Allow fsspec URLs in open_(mf)dataset 788398518 | |
| 764605415 | https://github.com/pydata/xarray/pull/4823#issuecomment-764605415 | https://api.github.com/repos/pydata/xarray/issues/4823 | MDEyOklzc3VlQ29tbWVudDc2NDYwNTQxNQ== | alexamici 226037 | 2021-01-21T12:19:24Z | 2021-01-21T12:19:24Z | MEMBER | @martindurant it is OK to let every backend raise errors for unsupported input. So no need to add any additional logic here IMO. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Allow fsspec URLs in open_(mf)dataset 788398518 |
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