issues

Table actions

3 rows where type = "pull" and user = 5572303 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
225222227 MDExOlB1bGxSZXF1ZXN0MTE4MjU1ODUw 1389 Sortby chunweiyuan 5572303 closed 0     28 2017-04-29T00:44:01Z 2017-05-12T18:36:30Z 2017-05-12T00:29:12Z CONTRIBUTOR   0 pydata/xarray/pulls/1389
  • [x] closes #967
  • [x] tests added / passed
  • [x] passes git diff upstream/master | flake8 --diff
  • [x] whatsnew entry
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1389/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
200478981 MDExOlB1bGxSZXF1ZXN0MTAxMzM5ODIw 1204 combine_first by using apply_ufunc in ops.fillna chunweiyuan 5572303 closed 0     9 2017-01-12T21:03:53Z 2017-01-23T22:43:32Z 2017-01-23T22:39:57Z CONTRIBUTOR   0 pydata/xarray/pulls/1204

Implementing ops.fillna using apply_ufunc, with a join kwarg. The new ops.fillna is then used to implement combine_first in both DataArray and Dataset objects.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1204/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
185794232 MDExOlB1bGxSZXF1ZXN0OTEyOTA5MzM= 1065 Options to binary ops kwargs chunweiyuan 5572303 closed 0     11 2016-10-27T22:17:16Z 2016-11-12T04:00:10Z 2016-11-12T03:59:42Z CONTRIBUTOR   0 pydata/xarray/pulls/1065

Currently the default is join="inner". However, there can be applications where the majority of binary operations require join="outer", not "inner".

Addresses https://github.com/pydata/xarray/issues/1059

The solution we come up with is adding a default key/value to OPTIONS, and dynamically access/update it in code (_binary_op in both dataarray.py and dataset.py)

We've also added test modules in test_dataarray.py and test_dataset.py. All tests passed.

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