issues

Table actions

2 rows where milestone = 1816292 and type = "issue" 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

  • issue · 2 ✖

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
166494079 MDU6SXNzdWUxNjY0OTQwNzk= 910 TODO: release v0.8.0 shoyer 1217238 closed 0   0.8.0 1816292 0 2016-07-20T04:35:20Z 2016-08-06T22:22:03Z 2016-08-06T22:22:03Z MEMBER      

I've been putting this off long enough -- we need to get all the recent work on xarray out there!

Things I'd like to merge first: - [x] xarray.merge function and major refactor for merge logic #857 - [x] Fix issue with expand_dims on 0d arrays of tuples #867 - [x] Refer users to Stack Overflow for support in the docs #922

Given the scope of these internal changes (especially #857), possibly a release candidate would be in order?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/910/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
168865176 MDU6SXNzdWUxNjg4NjUxNzY= 932 Doc: link to Internals in "what's new" fmaussion 10050469 closed 0   0.8.0 1816292 1 2016-08-02T11:43:34Z 2016-08-02T17:38:28Z 2016-08-02T17:38:22Z MEMBER      

Very minor issue, but the link to Internals in the latest what's new redirects to pandas', not xarray's.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/932/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue

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]);