issue_comments
2 rows where issue = 293272998 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Documentation is inaccessible via HTTPS · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 368622634 | https://github.com/pydata/xarray/issues/1873#issuecomment-368622634 | https://api.github.com/repos/pydata/xarray/issues/1873 | MDEyOklzc3VlQ29tbWVudDM2ODYyMjYzNA== | shoyer 1217238 | 2018-02-26T19:35:55Z | 2018-02-26T19:35:55Z | MEMBER | I don't particularly care about HTTPS for serving docs, but I think the desire is mostly to avoid scary looking error messages. If you could mirror the dask setup for xarray and sparse via cloudflare that would be appreciated. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Documentation is inaccessible via HTTPS 293272998 | |
| 368563183 | https://github.com/pydata/xarray/issues/1873#issuecomment-368563183 | https://api.github.com/repos/pydata/xarray/issues/1873 | MDEyOklzc3VlQ29tbWVudDM2ODU2MzE4Mw== | shoyer 1217238 | 2018-02-26T16:35:22Z | 2018-02-26T16:35:22Z | MEMBER | It looks like Dask has HTTPS configured properly for dask.pydata.org, so hopefully it's a simple fix for xarray, too. @mrocklin do you know how this was set up? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Documentation is inaccessible via HTTPS 293272998 |
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