issues

Table actions

4 rows where "closed_at" is on date 2022-09-28, type = "pull" and user = 43316012 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 · 4 ✖

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
1386664116 PR_kwDOAMm_X84_o0Jy 7087 Add typing to FacetGrid headtr1ck 43316012 closed 0     0 2022-09-26T20:16:26Z 2022-09-28T20:15:53Z 2022-09-28T18:30:59Z COLLABORATOR   0 pydata/xarray/pulls/7087

Mainly to annoy @Illviljan :)

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7087/reactions",
    "total_count": 4,
    "+1": 1,
    "-1": 0,
    "laugh": 3,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1389764085 PR_kwDOAMm_X84_zMRw 7102 Exclude typechecking stuff from coverage headtr1ck 43316012 closed 0     1 2022-09-28T18:12:39Z 2022-09-28T20:15:52Z 2022-09-28T19:18:54Z COLLABORATOR   0 pydata/xarray/pulls/7102

tiny PR that disables coverage on types.py and all typing-only imports a.la. if TYPE_CHECKING: ...

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7102/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1376479521 PR_kwDOAMm_X84_IJrz 7048 Add Ellipsis typehint to reductions headtr1ck 43316012 closed 0     8 2022-09-16T21:15:10Z 2022-09-28T18:02:51Z 2022-09-28T17:10:05Z COLLABORATOR   0 pydata/xarray/pulls/7048

This PR adds the ellipsis typehint to reductions (only where they behave differently from None to reduce overhead). Follow up on https://github.com/pydata/xarray/pull/7017#issuecomment-1243927061

Additionally I was changing a lot of "one or more dimensions" typehints to str | Iterable[Hashable] (See https://github.com/pydata/xarray/issues/6142). Some code changes were necessary to support this fully. Before several things were not working with actual hashable dimensions that are not strings.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7048/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1385143758 PR_kwDOAMm_X84_j6Bn 7080 Fix `utils.get_axis` with kwargs headtr1ck 43316012 closed 0     3 2022-09-25T19:50:15Z 2022-09-28T18:02:18Z 2022-09-28T17:11:16Z COLLABORATOR   0 pydata/xarray/pulls/7080
  • [x] Closes #7078
  • [x] Tests added
  • [x] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [x] ~~New functions/methods are listed in api.rst~~
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7080/reactions",
    "total_count": 1,
    "+1": 1,
    "-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]);