issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 903055859 and user = 5635139 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

  • max-sixty · 1 ✖

issue 1

  • Regression: "ValueError: cannot unstack dimensions that do not have a MultiIndex" when unstacking a MultiIndex · 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
849246165 https://github.com/pydata/xarray/issues/5384#issuecomment-849246165 https://api.github.com/repos/pydata/xarray/issues/5384 MDEyOklzc3VlQ29tbWVudDg0OTI0NjE2NQ== max-sixty 5635139 2021-05-27T01:31:49Z 2021-05-27T01:32:18Z MEMBER

This does look like a bug, specifically affecting MultiIndexes containing only one Index.

The issue seems to be that self.get_index('c') returns a normal index:

```python 4020 non_multi_dims = [ 4021 d for d in dims if not isinstance(self.get_index(d), pd.MultiIndex) 4022 ] 4023 if non_multi_dims: -> 4024 raise ValueError( 4025 "cannot unstack dimensions that do not " 4026 f"have a MultiIndex: {non_multi_dims}" 4027 ) 4028 4029 result = self.copy(deep=False) 4030 for dim in dims:

ipdb> self.get_index('c') Index([(0,)], dtype='object') # <- single index

ipdb> self <xarray.Dataset> Dimensions: (c: 1) Coordinates: * c (c) MultiIndex # <- multi index - b (c) int64 0 a (c) int64 0 Data variables: d (c) int64 0 ```

I'm not sure how common it is for MultiIndexes to have a single index, but we should be general over any number.

We'd definitely take a fix for this. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Regression: "ValueError: cannot unstack dimensions that do not have a MultiIndex" when unstacking a MultiIndex 903055859

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