issue_comments

Table actions

where issue = 479063574 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
534755294 https://github.com/pydata/xarray/pull/3199#issuecomment-534755294 https://api.github.com/repos/pydata/xarray/issues/3199 MDEyOklzc3VlQ29tbWVudDUzNDc1NTI5NA== shoyer 1217238 2019-09-24T21:26:04Z 2019-09-24T21:26:04Z MEMBER

Yikes, OK. Yes, it would be good to open an issue on the RTD GitHub page to discuss our options. --upgrade-strategy eager seems like a bad idea for us -- it really undermines the value of dependency pinning.

On Tue, Sep 24, 2019 at 1:31 PM keewis notifications@github.com wrote:

it seems all of these problems boil down to that single command. What gets executed is (essentially)

$ python -m pip install --upgrade --upgrade-strategy eager .

which upgrades pandas to 0.25.1, but leaves dask as is because it is an optional dependency. This, however, defeats the purpose of version pinning in the conda file (or a requirements file).

I can't find an option to tell readthedocs to install without the eager upgrade (normal upgrade is fine). Maybe ask support? The addition of the upgrade strategy happened in readthedocs/readthedocs.org#5635 https://github.com/readthedocs/readthedocs.org/pull/5635

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/pull/3199?email_source=notifications&email_token=AAJJFVULDVAUPID5WWAZAF3QLJ2JXA5CNFSM4IKVN6A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7PWUAY#issuecomment-534735363, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJJFVRI6S3TML3E27VEYNTQLJ2JXANCNFSM4IKVN6AQ . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add an example of ERA5 and GRIB data & visualization to the gallery 479063574
534343242 https://github.com/pydata/xarray/pull/3199#issuecomment-534343242 https://api.github.com/repos/pydata/xarray/issues/3199 MDEyOklzc3VlQ29tbWVudDUzNDM0MzI0Mg== shoyer 1217238 2019-09-24T01:03:38Z 2019-09-24T01:03:38Z MEMBER

Unfortunately, I don't think we can remove the second conda install. RTD insists on it to ensure that it has the build environment it needs. We could certainly ask on their GitHub support page, though.

On Mon, Sep 23, 2019 at 5:59 PM keewis notifications@github.com wrote:

(roughly) following the instructions in the build log, I can reproduce it raising a 404:

$ conda env create --quiet --name scipy19-docs --file doc/environment.yml $ conda install --yes --quiet --name scipy19-docs mock pillow sphinx sphinx_rtd_theme (scipy19-docs)$ python -m pip install -U recommonmark readthedocs-sphinx-ext (scipy19-docs)$ python setup.py install --force (scipy19-docs)$ cd doc; make html

I didn't check yet, but maybe the second conda install should not happen, as all those get installed on env creation?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/pull/3199?email_source=notifications&email_token=AAJJFVQVW3X5GAUBKXSBT7DQLFQ7LA5CNFSM4IKVN6A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7MWVIQ#issuecomment-534342306, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJJFVVKECGIALOX4DMWUSLQLFQ7LANCNFSM4IKVN6AQ . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add an example of ERA5 and GRIB data & visualization to the gallery 479063574

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