issues

Table actions

8 rows where type = "pull" and user = 11656932 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)

state 2

type 1

  • pull · 8 ✖

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
1982321440 PR_kwDOAMm_X85e28Ku 8424 Add support for remote string paths to `h5netcdf` engine jrbourbeau 11656932 open 0     15 2023-11-07T22:09:37Z 2024-01-05T06:25:44Z   CONTRIBUTOR   0 pydata/xarray/pulls/8424

cc @dcherian as you might find this interesting 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8424/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1562840229 PR_kwDOAMm_X85I1gYs 7489 Remove Dask single-threaded setting in tests jrbourbeau 11656932 closed 0     7 2023-01-30T17:13:16Z 2023-01-31T18:51:28Z 2023-01-31T18:45:47Z CONTRIBUTOR   0 pydata/xarray/pulls/7489

I'm not totally sure why single-threaded was being set to begin with, so I might be missing some important context here

Closes https://github.com/pydata/xarray/issues/7483 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7489/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1562931560 PR_kwDOAMm_X85I10MO 7491 Fix `isort` `pre-commit` install jrbourbeau 11656932 closed 0     2 2023-01-30T18:08:12Z 2023-01-30T18:16:15Z 2023-01-30T18:16:11Z CONTRIBUTOR   0 pydata/xarray/pulls/7491 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7491/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1368328647 PR_kwDOAMm_X84-tGZl 7016 `kwargs` typo in custom backend docs jrbourbeau 11656932 closed 0     1 2022-09-09T21:06:53Z 2022-09-09T22:37:10Z 2022-09-09T22:33:39Z CONTRIBUTOR   0 pydata/xarray/pulls/7016

Noticed a tiny typo when reading through https://docs.xarray.dev/en/stable/internals/how-to-add-new-backend.html

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7016/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1330548427 PR_kwDOAMm_X848v2u7 6884 Temporarily import `loop_in_thread` fixture from `distributed` jrbourbeau 11656932 closed 0     5 2022-08-05T22:30:53Z 2022-08-08T15:12:42Z 2022-08-06T01:25:19Z CONTRIBUTOR   0 pydata/xarray/pulls/6884

This is a quickfix similar to https://github.com/dask/dask/pull/9337. Note there's a conversation happening over in https://github.com/dask/distributed/issues/6806 around what testing utilities in distributed should be considered public. 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6884/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1103972043 PR_kwDOAMm_X84xDYL7 6166 Trigger upstream CI build jrbourbeau 11656932 closed 0     0 2022-01-14T18:06:23Z 2022-01-14T18:38:31Z 2022-01-14T18:38:28Z CONTRIBUTOR   0 pydata/xarray/pulls/6166

Just wanting to check the test suite before issuing a dask release. Apologies for the noise.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6166/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
983032639 MDExOlB1bGxSZXF1ZXN0NzIyNjgxMzEw 5751 Update `sparse` `test_chunk` xfail jrbourbeau 11656932 closed 0     3 2021-08-30T17:32:49Z 2021-08-31T15:12:45Z 2021-08-31T14:27:17Z CONTRIBUTOR   0 pydata/xarray/pulls/5751

xarray/tests/test_sparse.py::test_chunk now passes with the latest sparse=0.13.0 release

  • [x] Closes https://github.com/pydata/xarray/issues/5654
  • [ ] Tests added
  • [ ] Passes pre-commit run --all-files
  • [ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [ ] New functions/methods are listed in api.rst
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5751/reactions",
    "total_count": 5,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 5,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
877723396 MDExOlB1bGxSZXF1ZXN0NjMxNjI5NzI2 5271 Ensure `HighLevelGraph` layers are `Layer` instances jrbourbeau 11656932 closed 0     1 2021-05-06T16:46:48Z 2021-05-06T20:37:42Z 2021-05-06T20:29:55Z CONTRIBUTOR   0 pydata/xarray/pulls/5271

This PR updates how we construct the HighLevelGraph in subset_dataset_to_block. Currently we create a HighLevelGraph and then manually add a few new layers, which are dicts, directly to hlg.layers.

https://github.com/pydata/xarray/blob/eec2b59bd08498fe3d50d8549b540d0a8409c7ac/xarray/core/parallel.py#L537-L546

However since (in more recent versions of Dask) HighLevelGraph layers are expected to be Layer class instances this can result in unexpected errors (xref https://github.com/pydata/xarray/issues/5077#issuecomment-832359943). Instead of manually adding new layers to hlg.layers, this PR proposes we create a new HighLevelGraph altogether to ensure that hlg.layers won't contain any raw dict layers.

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