issues

Table actions

3 rows where type = "pull" and user = 23738400 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • pull · 3 ✖

state 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
1555829604 PR_kwDOAMm_X85IeHqq 7475 Update error message when saving multiindex OriolAbril 23738400 closed 0     0 2023-01-24T23:44:14Z 2023-02-25T11:57:59Z 2023-02-24T20:16:43Z CONTRIBUTOR   0 pydata/xarray/pulls/7475

I have updated the error message that gets printed when trying to save a multiindex following some discussion in an ArviZ repo with @dcherian.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7475/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1198717318 PR_kwDOAMm_X8418Vqw 6464 Add xarray-einstats to ecosystem page OriolAbril 23738400 closed 0     1 2022-04-09T17:12:37Z 2022-04-09T19:40:39Z 2022-04-09T19:37:01Z CONTRIBUTOR   0 pydata/xarray/pulls/6464

Adds a mention of xarray-einstats to the ecosystem page. Related to #3322.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6464/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
626215981 MDExOlB1bGxSZXF1ZXN0NDI0MjQ5MzI4 4103 keep attrs in reset_index OriolAbril 23738400 closed 0     7 2020-05-28T05:00:50Z 2020-06-05T19:42:54Z 2020-06-05T19:39:10Z CONTRIBUTOR   0 pydata/xarray/pulls/4103

Modifies the code in reset_index to keep attributes when converting an indexing coordinate to non indexing coordinate. I have added tests for single index for both dataarray and dataset. Not sure if both are needed as they end up calling the same base function.

Regarding multiindex, I think it is not possible to keep the metadata as it is removed when creating the multiindex/stacking.

  • [x] Closes #4101
  • [x] Tests added
  • [x] Passes isort -rc . && black . && mypy . && flake8
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4103/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);