issues
38 rows where comments = 3, type = "pull" and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1410303926 | PR_kwDOAMm_X85A3Xqk | 7163 | Add `eval` method to Dataset | max-sixty 5635139 | closed | 0 | 3 | 2022-10-15T22:12:23Z | 2023-12-06T17:52:47Z | 2023-12-06T17:52:46Z | MEMBER | 0 | pydata/xarray/pulls/7163 | This needs proper tests & docs, but would this be a good idea? A couple of examples are in the docstring. It's mostly just deferring to pandas' excellent
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/7163/reactions",
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 1
} |
xarray 13221727 | pull | |||||
| 2019309352 | PR_kwDOAMm_X85g0KvI | 8493 | Use numbagg for `rolling` methods | max-sixty 5635139 | closed | 0 | 3 | 2023-11-30T18:52:08Z | 2023-12-05T19:08:32Z | 2023-12-05T19:08:31Z | MEMBER | 0 | pydata/xarray/pulls/8493 | A couple of tests are failing for the multi-dimensional case, which I'll fix before merge. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8493/reactions",
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 1,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 2010795504 | PR_kwDOAMm_X85gXOqo | 8484 | Fix Zarr region transpose | max-sixty 5635139 | closed | 0 | 3 | 2023-11-25T21:01:28Z | 2023-11-27T20:56:57Z | 2023-11-27T20:56:56Z | MEMBER | 0 | pydata/xarray/pulls/8484 | This wasn't working on an unregion-ed write; I think because |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8484/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1948548087 | PR_kwDOAMm_X85dE9ga | 8329 | Request to adjust pyright config | max-sixty 5635139 | closed | 0 | 3 | 2023-10-18T01:04:00Z | 2023-10-18T20:10:42Z | 2023-10-18T20:10:41Z | MEMBER | 0 | pydata/xarray/pulls/8329 | Would it be possible to not have this config? It overrides the local VS Code config, and means VS Code constantly is reporting errors for me. Totally open to other approaches ofc. Or that we decide that the tradeoff is worthwhile |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8329/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1216647336 | PR_kwDOAMm_X8421oXV | 6521 | Move license from readme to LICENSE | max-sixty 5635139 | open | 0 | 3 | 2022-04-27T00:59:03Z | 2023-10-01T09:31:37Z | MEMBER | 0 | pydata/xarray/pulls/6521 | {
"url": "https://api.github.com/repos/pydata/xarray/issues/6521/reactions",
"total_count": 3,
"+1": 3,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||||
| 1903792930 | PR_kwDOAMm_X85auJN5 | 8215 | Use `TypeVar`s rather than specific unions | max-sixty 5635139 | closed | 0 | 3 | 2023-09-19T22:06:13Z | 2023-09-24T19:40:06Z | 2023-09-24T19:40:05Z | MEMBER | 0 | pydata/xarray/pulls/8215 | Also from the chars of #8208 -- this uses the TypeVars we define, which hopefully sets a standard and removes ambiguity for how to type functions. It also allows subclasses. Where possible, it uses |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8215/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1884999689 | PR_kwDOAMm_X85ZvD67 | 8156 | Cut middle version from CI | max-sixty 5635139 | closed | 0 | 3 | 2023-09-07T02:14:01Z | 2023-09-07T23:19:04Z | 2023-09-07T06:29:03Z | MEMBER | 0 | pydata/xarray/pulls/8156 | Testing for 3.10 seems fairly low value — is there a realistic case where 3.10 would fail but 3.9 & 3.11 would pass? Merging this would cut the CI queue... |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8156/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1221918339 | PR_kwDOAMm_X843Hi9Y | 6550 | Remove duplicate tests, v3 | max-sixty 5635139 | closed | 0 | 3 | 2022-04-30T20:50:01Z | 2022-04-30T23:22:22Z | 2022-04-30T22:47:47Z | MEMBER | 0 | pydata/xarray/pulls/6550 | Replaces https://github.com/pydata/xarray/pull/6541, which was using a branch in this repo, and so duplicating all the tests — which is fine but makes it difficult to understand what tests are being generated |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/6550/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1090177517 | PR_kwDOAMm_X84wWcc7 | 6121 | Change concat dims to be Hashable | max-sixty 5635139 | closed | 0 | 3 | 2021-12-28T23:35:14Z | 2022-01-11T22:18:33Z | 2022-01-10T22:13:22Z | MEMBER | 0 | pydata/xarray/pulls/6121 | A small typing change |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/6121/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1098449364 | PR_kwDOAMm_X84wwx9F | 6151 | Remove numpy from mypy pre-commit | max-sixty 5635139 | closed | 0 | 3 | 2022-01-10T22:22:14Z | 2022-01-11T15:20:08Z | 2022-01-10T23:52:51Z | MEMBER | 0 | pydata/xarray/pulls/6151 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/6151/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1076348620 | PR_kwDOAMm_X84vp1r4 | 6061 | Add release note skeleton for 0.21 | max-sixty 5635139 | closed | 0 | 3 | 2021-12-10T02:18:26Z | 2021-12-22T01:10:31Z | 2021-12-22T00:42:55Z | MEMBER | 0 | pydata/xarray/pulls/6061 | {
"url": "https://api.github.com/repos/pydata/xarray/issues/6061/reactions",
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | ||||||
| 1034285243 | PR_kwDOAMm_X84tlYLw | 5890 | Blacken notebooks | max-sixty 5635139 | closed | 0 | 3 | 2021-10-23T23:38:23Z | 2021-10-24T00:29:40Z | 2021-10-24T00:12:10Z | MEMBER | 0 | pydata/xarray/pulls/5890 |
The new version of black formats notebook files too, so I was getting diffs when doing other work. This should let us upgrade black in pre-commit when that comes out |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5890/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 987378623 | MDExOlB1bGxSZXF1ZXN0NzI2NDczMDA1 | 5761 | Fix pyi / py issue in mypy | max-sixty 5635139 | closed | 0 | 3 | 2021-09-03T04:11:31Z | 2021-09-13T00:28:50Z | 2021-09-13T00:03:35Z | MEMBER | 0 | pydata/xarray/pulls/5761 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5761/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 976214874 | MDExOlB1bGxSZXF1ZXN0NzE3MjA0NTU4 | 5729 | Xfail failing test on main | max-sixty 5635139 | closed | 0 | 3 | 2021-08-21T20:22:31Z | 2021-08-21T23:36:24Z | 2021-08-21T22:34:08Z | MEMBER | 0 | pydata/xarray/pulls/5729 | ref https://github.com/pydata/xarray/issues/5654 I vote to always do this when a dependency changes, if we can't immediately fix the code. Having main be green means it's easy to see the difference between passing and failing. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5729/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 967945936 | MDExOlB1bGxSZXF1ZXN0NzEwMDkyMzU3 | 5695 | Use isort's float-to-top | max-sixty 5635139 | closed | 0 | 3 | 2021-08-12T03:30:27Z | 2021-08-19T05:35:40Z | 2021-08-19T05:12:38Z | MEMBER | 0 | pydata/xarray/pulls/5695 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5695/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 522562906 | MDExOlB1bGxSZXF1ZXN0MzQwNzQwNjE2 | 3529 | Deprecation warning in _replace_vars_and_dims | max-sixty 5635139 | closed | 0 | 3 | 2019-11-14T01:09:34Z | 2021-05-13T22:01:45Z | 2021-05-13T22:01:45Z | MEMBER | 0 | pydata/xarray/pulls/3529 | & removed internal usages
I needed to pass |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3529/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 874038993 | MDExOlB1bGxSZXF1ZXN0NjI4NjczNDg5 | 5245 | xfail very flaky test | max-sixty 5635139 | closed | 0 | 3 | 2021-05-02T20:39:10Z | 2021-05-03T04:29:24Z | 2021-05-03T04:29:21Z | MEMBER | 0 | pydata/xarray/pulls/5245 | This consistently fails. In general I think as soon as we see this happening, we should either fix immediately (but probably not that easy) or xfail it and if necessary open an issue. That keeps the main branch green, such that we can reliably use passing tests as an indicator of PRs. Though as ever, very open to other thoughts. There's a reasonable argument that "keeping master green by removing any failing tests is missing the point a bit"... |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5245/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 862107086 | MDExOlB1bGxSZXF1ZXN0NjE4NzExMjQ2 | 5191 | Remove final raises_regexes | max-sixty 5635139 | closed | 0 | 3 | 2021-04-19T23:31:05Z | 2021-04-21T19:04:00Z | 2021-04-21T17:14:05Z | MEMBER | 0 | pydata/xarray/pulls/5191 |
~All apart from this issue, which is a puzzle. It would be great to remove the function, which requires solving that puzzle!~ Hacked around it, somewhat unsatisfactorily. But no need to delay this issue because of it. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5191/reactions",
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 860577067 | MDExOlB1bGxSZXF1ZXN0NjE3NDIzNTQy | 5184 | Enable clip broadcasting, with apply_ufunc | max-sixty 5635139 | closed | 0 | 3 | 2021-04-18T05:17:33Z | 2021-04-21T17:39:11Z | 2021-04-21T17:39:08Z | MEMBER | 0 | pydata/xarray/pulls/5184 |
I think this is the right approach — we may need to confirm the appropriate args to Tests are OK but a bit lacking atm. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5184/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 515106795 | MDExOlB1bGxSZXF1ZXN0MzM0NjE5ODE2 | 3472 | Type check sentinel values | max-sixty 5635139 | closed | 0 | 3 | 2019-10-31T02:15:57Z | 2021-04-19T06:10:36Z | 2019-10-31T15:52:02Z | MEMBER | 0 | pydata/xarray/pulls/3472 |
I did this before I realized it only works on mypy master! But posting so no one else does it. We can wait to merge until the next version of mypy is out |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3472/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 815845314 | MDExOlB1bGxSZXF1ZXN0NTc5NjA3MzQ4 | 4953 | Add 0.17.0 release notes | max-sixty 5635139 | closed | 0 | 3 | 2021-02-24T21:01:17Z | 2021-02-25T00:54:53Z | 2021-02-25T00:54:45Z | MEMBER | 0 | pydata/xarray/pulls/4953 | Let me know any changes here, fairly soon if possible! And please make changes liberally — what are the important features we should highlight in the heading? Thanks |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/4953/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 705185498 | MDExOlB1bGxSZXF1ZXN0NDg5OTU4NDE4 | 4443 | Fix release notes formatting | max-sixty 5635139 | closed | 0 | 3 | 2020-09-20T21:02:04Z | 2020-09-22T02:05:33Z | 2020-09-20T23:31:39Z | MEMBER | 0 | pydata/xarray/pulls/4443 | {
"url": "https://api.github.com/repos/pydata/xarray/issues/4443/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | ||||||
| 703991403 | MDExOlB1bGxSZXF1ZXN0NDg4OTk2Njk3 | 4433 | Clearer Vectorized Indexing example | max-sixty 5635139 | closed | 0 | 3 | 2020-09-18T00:21:33Z | 2020-09-18T18:36:36Z | 2020-09-18T15:23:33Z | MEMBER | 0 | pydata/xarray/pulls/4433 |
I found the existing example not that clear as to why it was selecting Before ```python In [37]: da = xr.DataArray( ....: np.arange(12).reshape((3, 4)), ....: dims=["x", "y"], ....: coords={"x": [0, 1, 2], "y": ["a", "b", "c", "d"]}, ....: ) ....: In [38]: da Out[38]: <xarray.DataArray (x: 3, y: 4)> array([[ 0, 1, 2, 3], [ 4, 5, 6, 7], [ 8, 9, 10, 11]]) Coordinates: * x (x) int64 0 1 2 * y (y) <U1 'a' 'b' 'c' 'd' In [39]: da[[0, 1], [1, 1]] Out[39]: <xarray.DataArray (x: 2, y: 2)> array([[1, 1], [5, 5]]) Coordinates: * x (x) int64 0 1 * y (y) <U1 'b' 'b' ``` After: ```python In [4]: da[[1, 2, 2], [0, 3]] Out[4]: <xarray.DataArray (x: 3, y: 2)> array([[ 4, 7], [ 8, 11], [ 8, 11]]) Coordinates: * x (x) int64 1 2 2 * y (y) <U1 'a' 'd'` ``` |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/4433/reactions",
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 589403798 | MDExOlB1bGxSZXF1ZXN0Mzk0OTYyMDY0 | 3905 | Limit length of dataarray reprs | max-sixty 5635139 | closed | 0 | 3 | 2020-03-27T20:45:08Z | 2020-07-11T20:33:56Z | 2020-06-24T16:04:12Z | MEMBER | 0 | pydata/xarray/pulls/3905 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3905/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 587197693 | MDExOlB1bGxSZXF1ZXN0MzkzMTkwMDIy | 3886 | Use `fixes` in PR template | max-sixty 5635139 | closed | 0 | 3 | 2020-03-24T18:37:06Z | 2020-03-28T19:50:12Z | 2020-03-24T18:48:36Z | MEMBER | 0 | pydata/xarray/pulls/3886 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3886/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 587099341 | MDExOlB1bGxSZXF1ZXN0MzkzMTA2MjY5 | 3885 | xfail test_uamiv_format_write | max-sixty 5635139 | closed | 0 | 3 | 2020-03-24T16:32:42Z | 2020-03-24T19:24:45Z | 2020-03-24T19:24:42Z | MEMBER | 0 | pydata/xarray/pulls/3885 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3885/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 584709888 | MDExOlB1bGxSZXF1ZXN0MzkxMjQ1NzI2 | 3870 | Fix html repr on non-str keys | max-sixty 5635139 | closed | 0 | 3 | 2020-03-19T21:26:36Z | 2020-03-20T17:04:30Z | 2020-03-20T17:04:26Z | MEMBER | 0 | pydata/xarray/pulls/3870 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3870/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 521314473 | MDExOlB1bGxSZXF1ZXN0MzM5NzE2MDA4 | 3511 | Format some of the docs code | max-sixty 5635139 | closed | 0 | 3 | 2019-11-12T04:00:23Z | 2019-11-12T16:04:50Z | 2019-11-12T04:31:39Z | MEMBER | 0 | pydata/xarray/pulls/3511 | I struggled to parse some of the code in the docs, and so formatted some of the hardest-to-read code (e.g. I'm not sure whether there's a more automated solution for this? On a related point, I'm not sure why some of the code examples are colorized and some are B&W? I couldn't see anything obvious in the rst.
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3511/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 448312915 | MDExOlB1bGxSZXF1ZXN0MjgyMTI2ODUz | 2988 | Remove deprecated pytest.config usages | max-sixty 5635139 | closed | 0 | 3 | 2019-05-24T19:00:11Z | 2019-06-14T23:06:46Z | 2019-05-25T02:01:32Z | MEMBER | 0 | pydata/xarray/pulls/2988 |
I need to confirm whether this works with an installed version of xarray, because of https://github.com/pytest-dev/pytest/issues/1596. If pytest doesn't pick up this config, it will run all tests, because the default is to not skip. I know I've generally been the point person for pytest - let me know if anyone has an immediate solution for this though |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2988/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 454787521 | MDExOlB1bGxSZXF1ZXN0Mjg3MTY4Mjk0 | 3016 | Pandas labels deprecation | max-sixty 5635139 | closed | 0 | 3 | 2019-06-11T16:24:43Z | 2019-06-12T00:49:31Z | 2019-06-11T22:58:26Z | MEMBER | 0 | pydata/xarray/pulls/3016 | Should I still add a |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3016/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 423493491 | MDExOlB1bGxSZXF1ZXN0MjYzMDU0Nzk4 | 2832 | Small fix: use == to compare strings | max-sixty 5635139 | closed | 0 | 3 | 2019-03-20T22:04:39Z | 2019-03-23T21:30:22Z | 2019-03-22T01:12:51Z | MEMBER | 0 | pydata/xarray/pulls/2832 |
(unless there's something I'm missing about |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2832/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 393978873 | MDExOlB1bGxSZXF1ZXN0MjQwODQzOTk2 | 2632 | Add flake check to travis | max-sixty 5635139 | closed | 0 | 3 | 2018-12-25T07:36:38Z | 2018-12-30T06:26:26Z | 2018-12-30T00:10:17Z | MEMBER | 0 | pydata/xarray/pulls/2632 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2632/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 373588302 | MDExOlB1bGxSZXF1ZXN0MjI1NDg0MDk2 | 2506 | Iterate over data_vars only | max-sixty 5635139 | closed | 0 | 3 | 2018-10-24T17:14:50Z | 2018-10-25T15:27:03Z | 2018-10-25T15:26:59Z | MEMBER | 0 | pydata/xarray/pulls/2506 |
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2506/reactions",
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 334942760 | MDExOlB1bGxSZXF1ZXN0MTk2Nzg2ODQ4 | 2246 | Small error in open_zarr docs | max-sixty 5635139 | closed | 0 | 3 | 2018-06-22T16:30:14Z | 2018-06-22T22:57:50Z | 2018-06-22T22:00:06Z | MEMBER | 0 | pydata/xarray/pulls/2246 | I tried setting this up on GCS as an experiment, and found there's no (also - if anyone has any experience in deploying xarray over https://github.com/dask/dask-kubernetes and GCS, I'd be interested in your experience. We're currently working with either a) BigQuery for big data or b) in-memory xarray for small data, and I was interested whether there's a way of retaining the xarray model for bigger data without too much overhead) |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2246/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 196844801 | MDExOlB1bGxSZXF1ZXN0OTg4NzEwMzg= | 1175 | End support for py3.3? | max-sixty 5635139 | closed | 0 | 3 | 2016-12-21T04:42:38Z | 2016-12-21T06:21:16Z | 2016-12-21T06:21:16Z | MEMBER | 0 | pydata/xarray/pulls/1175 | Even at the beginning of this year its downloads were 90% lower than 2.6: https://hynek.me/articles/python3-2016/ Impetus is that pytest no longer supports it, and some of the tests I recently wrote don't work on 3.3 |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/1175/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 131219763 | MDExOlB1bGxSZXF1ZXN0NTgyMzMzMTg= | 746 | BUG: Don't transpose variables of one dimension | max-sixty 5635139 | closed | 0 | 3 | 2016-02-04T02:29:06Z | 2016-02-09T16:46:40Z | 2016-02-09T16:05:28Z | MEMBER | 0 | pydata/xarray/pulls/746 | Resolves https://github.com/pydata/xarray/issues/745 A bit of a 'convenient hack'. Let me know if you think there's a better way to do this |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/746/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 124578622 | MDExOlB1bGxSZXF1ZXN0NTQ5MDIzNTk= | 698 | Allow empty DataFrame in Dataset construction | max-sixty 5635139 | closed | 0 | 3 | 2016-01-02T07:01:58Z | 2016-01-02T07:34:42Z | 2016-01-02T07:26:29Z | MEMBER | 0 | pydata/xarray/pulls/698 | Closes https://github.com/xray/xray/issues/697 @shoyer: am I missing something as to why the special case was there? |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/698/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 120513074 | MDExOlB1bGxSZXF1ZXN0NTI3Mzg3NTQ= | 671 | Align pandas objects with named indexes | max-sixty 5635139 | closed | 0 | 3 | 2015-12-05T00:20:41Z | 2015-12-10T22:38:33Z | 2015-12-08T07:23:41Z | MEMBER | 0 | pydata/xarray/pulls/671 | closes https://github.com/xray/xray/issues/664. What's new & docs forthcoming |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/671/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]);
