issue_comments

Table actions

2 rows where issue = 146079798 and user = 6488896 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • tsaoyu · 2 ✖

issue 1

  • modified: xarray/backends/api.py · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
388749495 https://github.com/pydata/xarray/pull/817#issuecomment-388749495 https://api.github.com/repos/pydata/xarray/issues/817 MDEyOklzc3VlQ29tbWVudDM4ODc0OTQ5NQ== tsaoyu 6488896 2018-05-14T09:11:08Z 2018-05-14T09:11:08Z NONE

I am trying to understand the logic by looking through the comments/discussion on this commit. After two years of development, there are quite some changes on the API itself e.g. the logic on the gzipped file handling seems already moved from api.py to scipy_.py. So I think it would be better to start a new commit from the latest version.

To bring the concept on the same table, there are 3 backends that can be used to handle gzipped netCDF file namely scipy, netcdf4 and pydap. scipy backend only support netCDF3 so far and that is the only implemented method to handle gzipped netCDF3 file. netcdf4 and pydap should able to deal with netCDF4 file given the file is first opened by gzip.open (as it was implement in scipy_.py).

So what we need to do is to make both netCDF4_.py and pydap_.py aware of the file is end with .gz and first open it using gzip.open. Following tests also need to be done to verify the implementation of the logic. I have looked at vcrpy and it seems a nice idea to speed up tests with HTTP stuff involved. I must confess I only use xarray with local file so it may takes quite a while to understand the issue. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   modified: xarray/backends/api.py 146079798
388386642 https://github.com/pydata/xarray/pull/817#issuecomment-388386642 https://api.github.com/repos/pydata/xarray/issues/817 MDEyOklzc3VlQ29tbWVudDM4ODM4NjY0Mg== tsaoyu 6488896 2018-05-11T14:49:48Z 2018-05-11T14:49:48Z NONE

How is this issue progressed so far? I am running into the same problem now and I might able to offer some help in testing. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   modified: xarray/backends/api.py 146079798

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