issues

Table actions

3 rows where user = 280924 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 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
420139027 MDU6SXNzdWU0MjAxMzkwMjc= 2807 can the callables of apply_ufunc + dask get a typed/labeled array ttung 280924 closed 0     5 2019-03-12T18:22:25Z 2019-10-15T15:01:08Z 2019-10-15T15:01:08Z CONTRIBUTOR      

Code Sample

```python def print_type(arr): """Generalized ufunc to print the type.""" print(f"type={type(arr)}") return arr

chunked = da.from_array(np.random.random(size=(2, 2, 2, 140, 200)), chunks=(1, 1, 1, 140, 200))

x = xr.DataArray(chunked) xr.apply_ufunc(print_type, x, dask='parallelized', output_dtypes=[np.float32]).compute() ```

Problem description

It would be great if the arrays passed to the callables were subselections of the original xarray. Advantages: labeled dimensions and coordinates

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2807/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
495974092 MDExOlB1bGxSZXF1ZXN0MzE5NDE5NTQ4 3325 Fix DataArray.to_netcdf type annotation ttung 280924 closed 0     1 2019-09-19T19:01:56Z 2019-09-27T05:45:34Z 2019-09-27T05:45:26Z CONTRIBUTOR   0 pydata/xarray/pulls/3325

It calls DataSet.to_netcdf, which returns Union[bytes, "Delayed", None]. So this should as well.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3325/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
347503891 MDExOlB1bGxSZXF1ZXN0MjA2MTEzMzQ3 2339 Use sorted fixtures to ensure that test gathering is consistent. ttung 280924 closed 0     0 2018-08-03T19:01:28Z 2018-08-06T14:57:16Z 2018-08-06T14:57:16Z CONTRIBUTOR   0 pydata/xarray/pulls/2339

pytest-xdist expects that test gathering produces the same results and in the same order. Because sets, prior to python 3.7, do not guarantee ordering, this can cause pytest -n (from pytest-xdist) to fail.

  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later)
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2339/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]);