issues

Table actions

4 rows where state = "closed", type = "pull" and user = 41342785 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • pull · 4 ✖

state 1

  • closed · 4 ✖

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
847376965 MDExOlB1bGxSZXF1ZXN0NjA2Mzk1NDky 5100 Tweaked Dataset.plot docs to better describe quiver cspencerjones 41342785 closed 0     1 2021-03-31T21:33:48Z 2021-05-01T17:40:06Z 2021-04-01T16:44:23Z CONTRIBUTOR   0 pydata/xarray/pulls/5100

closes #5002

Based on issue #5002, I did a few tweaks to make it clearer which parts of the generated documentation apply to quiver, and which apply to scatter. I also removed references to contourf because that is now documented in a separate location. 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5100/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
484768136 MDExOlB1bGxSZXF1ZXN0MzEwNTc2Mzc2 3259 New feature of filter_by_attrs added to whats-new.rst cspencerjones 41342785 closed 0     1 2019-08-24T02:28:05Z 2019-08-24T03:20:59Z 2019-08-24T03:20:59Z CONTRIBUTOR   0 pydata/xarray/pulls/3259

I missed this in my previous pull request. @dcherian

  • [ ] Closes #xxxx
  • [ ] Tests added
  • [ ] Passes black . && mypy . && flake8
  • [ ] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3259/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
484243962 MDExOlB1bGxSZXF1ZXN0MzEwMTY2MDYz 3247 Update filter_by_attrs to use 'variables' instead of 'data_vars' cspencerjones 41342785 closed 0     8 2019-08-22T22:23:31Z 2019-08-23T23:27:03Z 2019-08-23T23:26:00Z CONTRIBUTOR   0 pydata/xarray/pulls/3247

This will allow filter_by_attrs to filter coordinates as well as variables. @ocefpaf

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3247/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
484623632 MDExOlB1bGxSZXF1ZXN0MzEwNDYyOTI1 3253 Updater to testing environment name cspencerjones 41342785 closed 0     1 2019-08-23T16:55:49Z 2019-08-23T17:00:40Z 2019-08-23T17:00:40Z CONTRIBUTOR   0 pydata/xarray/pulls/3253

The testing environment name has been updated to xarray-tests in the package and we should do this in the documentation as well.

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