issue_comments

Table actions

3 rows where issue = 891281614 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Suggesting specific IO backends to install when open_dataset() fails · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
840901043 https://github.com/pydata/xarray/issues/5302#issuecomment-840901043 https://api.github.com/repos/pydata/xarray/issues/5302 MDEyOklzc3VlQ29tbWVudDg0MDkwMTA0Mw== shoyer 1217238 2021-05-13T23:57:16Z 2021-05-13T23:57:16Z MEMBER

Another advantage of "always registering" backends is that I think it will make for a better user-experience when installing a new dependency for IO via pip, because they won't have to restart their Python session: https://github.com/pydata/xarray/issues/5291#issuecomment-840900432

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Suggesting specific IO backends to install when open_dataset() fails 891281614
840897202 https://github.com/pydata/xarray/issues/5302#issuecomment-840897202 https://api.github.com/repos/pydata/xarray/issues/5302 MDEyOklzc3VlQ29tbWVudDg0MDg5NzIwMg== shoyer 1217238 2021-05-13T23:44:03Z 2021-05-13T23:44:03Z MEMBER

Sounds good, I'll make a short-term fix for the tutorial data

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Suggesting specific IO backends to install when open_dataset() fails 891281614
840820163 https://github.com/pydata/xarray/issues/5302#issuecomment-840820163 https://api.github.com/repos/pydata/xarray/issues/5302 MDEyOklzc3VlQ29tbWVudDg0MDgyMDE2Mw== aurghs 35919497 2021-05-13T20:39:14Z 2021-05-13T20:39:14Z COLLABORATOR

Me too, I was thinking about something like that to fix the error message.
Let me try to implement it. But I have really no time this week and the next one, sorry. I can do it after 23th if for you is ok. 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Suggesting specific IO backends to install when open_dataset() fails 891281614

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