issue_comments

Table actions

12 rows where issue = 293272998 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

issue 1

  • Documentation is inaccessible via HTTPS · 12 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
371429866 https://github.com/pydata/xarray/issues/1873#issuecomment-371429866 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM3MTQyOTg2Ng== hameerabbasi 2190658 2018-03-08T09:24:20Z 2018-03-08T09:24:20Z MEMBER

Things look fine now. :-)

 
{
    "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
368686880 https://github.com/pydata/xarray/issues/1873#issuecomment-368686880 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODY4Njg4MA== jhamman 2443309 2018-02-26T23:20:27Z 2018-02-26T23:20:27Z MEMBER

Thanks @aterrel! 

{
    "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
368686838 https://github.com/pydata/xarray/issues/1873#issuecomment-368686838 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODY4NjgzOA== jhamman 2443309 2018-02-26T23:20:17Z 2018-02-26T23:20:17Z MEMBER

This seems to be working, @hameerabbasi - can you confirm and close if things look okay on your end. 

{
    "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
368628179 https://github.com/pydata/xarray/issues/1873#issuecomment-368628179 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODYyODE3OQ== aterrel 30583 2018-02-26T19:52:47Z 2018-02-26T19:52:47Z MEMBER

Okay I'll turn on the HTTPS proxy service. Let me know if you notice anything unexpected.

 
{
    "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
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
368618714 https://github.com/pydata/xarray/issues/1873#issuecomment-368618714 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODYxODcxNA== hameerabbasi 2190658 2018-02-26T19:24:34Z 2018-02-26T19:24:34Z MEMBER

xref pydata/sparse#103

 
{
    "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
368575586 https://github.com/pydata/xarray/issues/1873#issuecomment-368575586 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODU3NTU4Ng== aterrel 30583 2018-02-26T17:11:41Z 2018-02-26T17:11:41Z MEMBER

Hello if you find troubles with pydata.org definitely send mail to web@pydata.org

In this case, which is completely different from the Dask cask, xarray.pydata.org is registered as a cname to read the docs. While pydata.org does serve via Nginx subdomains do not point to that server.

Read the docs is serving a security certificate with itself as the domain authority. The browser correctly recognizes that this is not the correct certificate for a custom domain, (only really good for things like: https://readthedocs.org/projects/xray/)

If there is a desire to serve a https from the xdata.pydata.org, I can set up a certificate on cloudflare which will terminate the https request and forward the http request to readthedocs. As Dask has found there is a bug somewhere that redirects some pages on read the docs from https to http, but we can cross that bridgw when we get there.

 
{
    "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
368575548 https://github.com/pydata/xarray/issues/1873#issuecomment-368575548 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODU3NTU0OA== mrocklin 306380 2018-02-26T17:11:32Z 2018-02-26T17:11:32Z MEMBER

From Anaconda's David Mason (I don't know his github handle):

Readthedocs has confirmed that they have a bug with the way they are handling redirections on their community site. They opened their own bug ticket to work on resolving the issue.

 
{
    "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
368569053 https://github.com/pydata/xarray/issues/1873#issuecomment-368569053 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODU2OTA1Mw== mrocklin 306380 2018-02-26T16:52:21Z 2018-02-26T16:52:21Z MEMBER

Not really, no. I tend to push these upstream to either Anaconda's IT or NumFOCUS. cc @aterrel 

{
    "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
368561525 https://github.com/pydata/xarray/issues/1873#issuecomment-368561525 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODU2MTUyNQ== hameerabbasi 2190658 2018-02-26T16:30:27Z 2018-02-26T16:30:27Z MEMBER

I have experience with Nginx, which PyData uses (according to some HTTP headers).

 
{
    "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
368385404 https://github.com/pydata/xarray/issues/1873#issuecomment-368385404 https://api.github.com/repos/pydata/xarray/issues/1873 MDEyOklzc3VlQ29tbWVudDM2ODM4NTQwNA== jhamman 2443309 2018-02-26T04:13:45Z 2018-02-26T04:13:45Z MEMBER

Does anyone have experience configuring https certificates with either pydata.org or RTD?

 
{
    "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

CSV options: 

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]);