issue_comments

Table actions

4 rows where author_association = "MEMBER", issue = 275744315 and user = 1197350 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 1

  • rabernat · 4 ✖

issue 1

  • IndexError when printing dataset from an Argo file · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
346120371 https://github.com/pydata/xarray/issues/1732#issuecomment-346120371 https://api.github.com/repos/pydata/xarray/issues/1732 MDEyOklzc3VlQ29tbWVudDM0NjEyMDM3MQ== rabernat 1197350 2017-11-21T18:36:49Z 2017-11-21T18:36:49Z MEMBER

Currently, xarray does not handle such zero-length n-dimensional arrays. Maybe we need to drop such variables when reading?

Rather than drop a variable the user could read with no problem under xarray 0.9.6, I propose we examine our new indexing wrappers and figure out how to fix this bug.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   IndexError when printing dataset from an Argo file 275744315
346072873 https://github.com/pydata/xarray/issues/1732#issuecomment-346072873 https://api.github.com/repos/pydata/xarray/issues/1732 MDEyOklzc3VlQ29tbWVudDM0NjA3Mjg3Mw== rabernat 1197350 2017-11-21T16:00:58Z 2017-11-21T16:00:58Z MEMBER

~It's good to see that the release-candidate process actually works!~ 😭 

{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 1,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   IndexError when printing dataset from an Argo file 275744315
346059225 https://github.com/pydata/xarray/issues/1732#issuecomment-346059225 https://api.github.com/repos/pydata/xarray/issues/1732 MDEyOklzc3VlQ29tbWVudDM0NjA1OTIyNQ== rabernat 1197350 2017-11-21T15:20:21Z 2017-11-21T15:20:21Z MEMBER

It's good to see that the release-candidate process actually works! 😉 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   IndexError when printing dataset from an Argo file 275744315
346056557 https://github.com/pydata/xarray/issues/1732#issuecomment-346056557 https://api.github.com/repos/pydata/xarray/issues/1732 MDEyOklzc3VlQ29tbWVudDM0NjA1NjU1Nw== rabernat 1197350 2017-11-21T15:12:28Z 2017-11-21T15:12:38Z MEMBER

Guillaume--this is very troubling! I use xarray frequently on ARGO netCDF files. It would be a shame if we broke something related to reading them. It sounds like this could be related to the indexing changes in #1676.

Since rc1, xarray 0.10.0 has gone through another release candidate (rc2) and is now in full release. Can you try upgrading to the just-released 0.10.0 and verify whether the problem is still present?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   IndexError when printing dataset from an Argo file 275744315

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