issues

Table actions

3 rows where comments = 10, type = "pull" 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), 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
1865945636 PR_kwDOAMm_X85YvIJ4 8114 Move `.rolling_exp` functions from `reduce` to `apply_ufunc` max-sixty 5635139 closed 0     10 2023-08-24T21:57:19Z 2023-09-19T01:13:27Z 2023-09-19T01:13:22Z MEMBER   0 pydata/xarray/pulls/8114
  • [x] Fixes #6870
  • [x] User visible changes (including notable bug fixes) are documented in whats-new.rst

A similar change should solve #6528, but let's get one finished first...

~Posting for discussion, will comment inline~ Ready for merge

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8114/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
325609580 MDExOlB1bGxSZXF1ZXN0MTg5OTAwNDA1 2174 Datasets more robust to non-string keys max-sixty 5635139 closed 0     10 2018-05-23T08:53:36Z 2018-05-28T01:44:02Z 2018-05-27T20:48:31Z MEMBER   0 pydata/xarray/pulls/2174
  • [x] Closes #2172 & #2173
  • [x] Tests added
  • [x] Tests passed
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API

I don't think this is the most efficient way of doing this, though it does work. Any ideas for a more efficient implementation?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2174/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
298437967 MDExOlB1bGxSZXF1ZXN0MTcwMDc4MTkw 1924 isort max-sixty 5635139 closed 0     10 2018-02-20T00:32:51Z 2018-02-27T19:33:38Z 2018-02-27T19:33:35Z MEMBER   0 pydata/xarray/pulls/1924

Not sure if we want this?

Probably too strict to enforce on every commit, more permissible to do a one-time update, assuming it doesn't cause merge conflicts.

You can get the same result by running isort -y

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1924/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]);