issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 1288323549 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

  • better handling of invalid files in open_mfdataset · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1170145563 https://github.com/pydata/xarray/issues/6736#issuecomment-1170145563 https://api.github.com/repos/pydata/xarray/issues/6736 IC_kwDOAMm_X85FvwEb dcherian 2448579 2022-06-29T15:44:20Z 2022-06-29T15:44:20Z MEMBER

t would be most useful to this particular user if the error message could somehow identify the file(s) responsible for the exception.

+1. You could make this change to open_dataset and it will be raised with open_mfdataset too. Attempting to read a bad netCDF file is a common source of trouble. So an error saying something like

Reading file XXX failed. The file is possibly corrupted, or the file path is wrong.

would be quite helpful!

I would find it very useful if I could pass to open_mfdataset some kind of argument that would make it ignore invalid files altogether (ignore_invalid=False comes to mind).

This I'm not sure about because a user wouldn't know if they were missing some data in the middle...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   better handling of invalid files in open_mfdataset 1288323549

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