issue_comments

Table actions

4 rows where issue = 208431831 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Switch AppVeyor CI to use conda env / requirements.yml · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
281185495 https://github.com/pydata/xarray/pull/1274#issuecomment-281185495 https://api.github.com/repos/pydata/xarray/issues/1274 MDEyOklzc3VlQ29tbWVudDI4MTE4NTQ5NQ== shoyer 1217238 2017-02-20T21:30:17Z 2017-02-20T21:30:17Z MEMBER

Looks great, thanks!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Switch AppVeyor CI to use conda env / requirements.yml 208431831
280812037 https://github.com/pydata/xarray/pull/1274#issuecomment-280812037 https://api.github.com/repos/pydata/xarray/issues/1274 MDEyOklzc3VlQ29tbWVudDI4MDgxMjAzNw== spencerkclark 6628425 2017-02-18T01:51:46Z 2017-02-18T01:51:46Z MEMBER

Cool, I think I have things working now. Please let me know if you'd like me to make any changes.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Switch AppVeyor CI to use conda env / requirements.yml 208431831
280735095 https://github.com/pydata/xarray/pull/1274#issuecomment-280735095 https://api.github.com/repos/pydata/xarray/issues/1274 MDEyOklzc3VlQ29tbWVudDI4MDczNTA5NQ== shoyer 1217238 2017-02-17T18:53:59Z 2017-02-17T18:53:59Z MEMBER

If it's a matter of simply creating new requirements files for the Windows environments to mirror what was installed in the original appveyor.yml file, i.e. pip, pytest, numpy, pandas, scipy, netCDF4, matplotlib, and dask, (this time using the conda-forge channel) then I can probably handle that

Yes, this is what I would recommend. It's just a little easier to maintain if we keep the requirements separate from the install script.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Switch AppVeyor CI to use conda env / requirements.yml 208431831
280643863 https://github.com/pydata/xarray/pull/1274#issuecomment-280643863 https://api.github.com/repos/pydata/xarray/issues/1274 MDEyOklzc3VlQ29tbWVudDI4MDY0Mzg2Mw== spencerkclark 6628425 2017-02-17T13:05:30Z 2017-02-17T13:05:30Z MEMBER

@shoyer it's entirely possible I'm in over my head here, as I'm not a Windows user, so I can't test this setup locally. It looks as though using the existing requirements files (which install more than what was specified in the original appveyor.yml configuration file) was probably not a good idea.

If it's a matter of simply creating new requirements files for the Windows environments to mirror what was installed in the original appveyor.yml file, i.e. pip, pytest, numpy, pandas, scipy, netCDF4, matplotlib, and dask, (this time using the conda-forge channel) then I can probably handle that, but anything more is guesswork on my end, so I'd be fine closing this PR. I was hoping for a straightforward fix.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Switch AppVeyor CI to use conda env / requirements.yml 208431831

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