issues
6 rows where repo = 13221727, type = "pull" and user = 691772 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: comments, body, created_at (date), updated_at (date), closed_at (date)
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 467494277 | MDExOlB1bGxSZXF1ZXN0Mjk3MTM2MjEz | 3104 | Fix minor typos in documentation | lumbric 691772 | closed | 0 | 2 | 2019-07-12T16:13:15Z | 2019-07-12T16:53:28Z | 2019-07-12T16:51:54Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/3104 | {
"url": "https://api.github.com/repos/pydata/xarray/issues/3104/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | ||||||
| 467482848 | MDExOlB1bGxSZXF1ZXN0Mjk3MTI2ODgw | 3103 | Add missing assert to unit test | lumbric 691772 | closed | 0 | 1 | 2019-07-12T15:46:20Z | 2019-07-12T16:35:16Z | 2019-07-12T16:35:16Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/3103 | Stumbled upon a unit test which didn't test anything. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3103/reactions",
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 434444058 | MDExOlB1bGxSZXF1ZXN0MjcxNDM1NjU4 | 2904 | Minor improvement of docstring for Dataset | lumbric 691772 | closed | 0 | 6 | 2019-04-17T19:16:50Z | 2019-04-17T20:09:26Z | 2019-04-17T20:08:46Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/2904 | This might help to avoid confusion. data_vars is always a mapping, not a mapping, a variable or a tuple. Passing just a tuple, does not work of course. But for xarray newbies, this might be less obvious and the error message is also not easy to interpret: ```
The correct version of the example above should be: ```
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2904/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 434439562 | MDExOlB1bGxSZXF1ZXN0MjcxNDMyMTc5 | 2903 | Fix minor typos in docstrings | lumbric 691772 | closed | 0 | 1 | 2019-04-17T19:05:47Z | 2019-04-17T19:15:10Z | 2019-04-17T19:15:10Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/2903 | See also pull-request #2860 - the same typo was at many places. Sorry, I have missed the other places when sending the first PR. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2903/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 427604384 | MDExOlB1bGxSZXF1ZXN0MjY2MTYyNTQw | 2860 | Fix minor typo in docstring | lumbric 691772 | closed | 0 | 1 | 2019-04-01T09:35:02Z | 2019-04-01T11:18:40Z | 2019-04-01T11:18:29Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/2860 | {
"url": "https://api.github.com/repos/pydata/xarray/issues/2860/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | ||||||
| 389685381 | MDExOlB1bGxSZXF1ZXN0MjM3NjE4MzYx | 2598 | Fix wrong error message in interp() | lumbric 691772 | closed | 0 | 2 | 2018-12-11T10:09:53Z | 2018-12-11T19:29:03Z | 2018-12-11T19:29:03Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/2598 | This is just a minor fix of a wrong error message. Please let me know if you think that this is worth testing in unit tests. Before: ```
After: ```
ValueError: the first argument to .interp must be a dictionary ``` |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2598/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
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]);