issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 441222339 and user = 1217238 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

  • shoyer · 2 ✖

issue 1

  • std interprets continents as zero not nan · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
490590509 https://github.com/pydata/xarray/issues/2946#issuecomment-490590509 https://api.github.com/repos/pydata/xarray/issues/2946 MDEyOklzc3VlQ29tbWVudDQ5MDU5MDUwOQ== shoyer 1217238 2019-05-08T18:06:04Z 2019-05-08T18:06:04Z MEMBER

It sounds like this is an issue that only comes up when using open_mfdataset? Is so, this indicating that the problem is likely somehow related to using dask arrays.

It be nice to have a minimal example of what goes wrong that doesn't require reading/writing netCDF files. Can you construct a synthetic dataset in memory that exhibits this problem? Note that you can use the .chunk() method to chunk arrays with dask.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   std interprets continents as zero not nan 441222339
490375850 https://github.com/pydata/xarray/issues/2946#issuecomment-490375850 https://api.github.com/repos/pydata/xarray/issues/2946 MDEyOklzc3VlQ29tbWVudDQ5MDM3NTg1MA== shoyer 1217238 2019-05-08T07:13:28Z 2019-05-08T07:13:28Z MEMBER

Can you reproduce this with a synthetic dataset? Please read this guide on "Minimal Bug Reports": http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   std interprets continents as zero not nan 441222339

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