home / github

Menu
  • Search all tables
  • GraphQL API

issues

Table actions
  • GraphQL API for issues

5 rows where comments = 8 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 5

state 1

  • closed 5

repo 1

  • xarray 5
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
1401132297 PR_kwDOAMm_X85AZG38 7142 Fix Codecov headtr1ck 43316012 closed 0     8 2022-10-07T12:55:00Z 2023-08-30T18:58:19Z 2023-08-30T18:47:33Z COLLABORATOR   0 pydata/xarray/pulls/7142
  • [x] Closes #7141
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7142/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    xarray 13221727 pull
1421441672 PR_kwDOAMm_X85BcmP0 7209 Optimize some copying headtr1ck 43316012 closed 0     8 2022-10-24T21:00:21Z 2022-12-08T20:09:49Z 2022-11-30T23:36:56Z COLLABORATOR   0 pydata/xarray/pulls/7209
  • [x] Potentially closes #7181
  • [x] Tests added
  • [ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

I have passed along some more memo dicts, which could prevent some double deep-copying of the same data (don't know how exactly, but who knows :P) Also, I have found some copy calls that did not pass along the deep argument (I am not sure if that breaks things, lets find out). And finally I have found some places where shallow copies are enough.

All together it should improve the performance a lot when copying things around.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7209/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
1315959612 PR_kwDOAMm_X847_0k6 6821 Fix numpy 1.20 incompatibility headtr1ck 43316012 closed 0     8 2022-07-24T17:10:24Z 2022-08-20T17:01:13Z 2022-07-30T21:11:08Z COLLABORATOR   0 pydata/xarray/pulls/6821

This PR removes the _SupportsDType dependency from numpy and introduces its own.

Closes https://github.com/pydata/xarray/issues/6818

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6821/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    xarray 13221727 pull
1292091752 PR_kwDOAMm_X846vljd 6744 Fix `DataArrayRolling.__iter__` with `center=True` headtr1ck 43316012 closed 0     8 2022-07-02T16:36:00Z 2022-07-18T15:31:54Z 2022-07-14T17:41:01Z COLLABORATOR   0 pydata/xarray/pulls/6744
  • [x] Closes #6739
  • [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~~

I have taken the freedom to move all rolling related tests into their own testing module. https://github.com/pydata/xarray/pull/6730 should then take care of the (by now) copy-pasted da and ds fixtures.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6744/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]);
Powered by Datasette · Queries took 205.55ms · About: xarray-datasette