issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 352909556 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

issue 1

  • File written by to_netcdf() not closed when Dataset is generated from dask delayed object using a dask Client() · 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
419309486 https://github.com/pydata/xarray/issues/2376#issuecomment-419309486 https://api.github.com/repos/pydata/xarray/issues/2376 MDEyOklzc3VlQ29tbWVudDQxOTMwOTQ4Ng== shoyer 1217238 2018-09-07T03:16:46Z 2018-09-07T03:16:46Z MEMBER

I think the short answer for how to work around this with the current version of xarray is to set the HDF5_USE_FILE_LOCKING environment variable, e.g., python import os os.environ['HDF5_USE_FILE_LOCKING'] = 'FALSE'

But this should be solved by #2261 regardless.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   File written by to_netcdf() not closed when Dataset is generated from dask delayed object using a dask Client() 352909556
415200809 https://github.com/pydata/xarray/issues/2376#issuecomment-415200809 https://api.github.com/repos/pydata/xarray/issues/2376 MDEyOklzc3VlQ29tbWVudDQxNTIwMDgwOQ== shoyer 1217238 2018-08-22T22:20:54Z 2018-08-22T22:20:54Z MEMBER

Thanks for the report. I can confirm this on the latest development version of xarray, so I'm marking this as a bug.

It looks like this will be fixed by https://github.com/pydata/xarray/pull/2261. At least with my local tests, that using the branch from that PR seems to fix the issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   File written by to_netcdf() not closed when Dataset is generated from dask delayed object using a dask Client() 352909556

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