issues

Table actions

2 rows where state = "closed" and user = 15901813 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

  • closed · 2 ✖

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
146812468 MDU6SXNzdWUxNDY4MTI0Njg= 820 Dataset.__repr__ causing dask to be computed. andrewdhicks 15901813 closed 0     3 2016-04-08T04:43:18Z 2019-10-01T04:18:38Z 2019-10-01T04:18:37Z NONE      

Printing a Dataset object will show array values (#206), but it will also cause a dask-backed array to be computed so that the data variable values can be computed:

<xarray.Dataset> Dimensions: (time: 182, x: 420, y: 489) Coordinates: * time (time) datetime64[ns] 1990-03-02T23:11:16 1990-03-02T23:11:39 ... * y (y) float64 -3.919e+06 -3.919e+06 -3.919e+06 -3.919e+06 ... * x (x) float64 1.538e+06 1.538e+06 1.538e+06 1.538e+06 1.538e+06 ... Data variables: band_20 (time, y, x) float64 729.0 612.0 579.0 629.0 862.0 1.027e+03 ... band_10 (time, y, x) float64 476.0 375.0 357.0 416.0 586.0 708.0 730.0 ... band_50 (time, y, x) float64 2.175e+03 634.0 245.0 546.0 1.788e+03 ... ...

When a DataArray is printed, it doesn't compute values when using dask:

<xarray.DataArray u'ls5_nbar_albers' (time: 182, y: 489, x: 420)> dask.array<concate..., shape=(182, 489, 420), dtype=float64, chunksize=(1, 489, 420)> Coordinates: * time (time) datetime64[ns] 1990-03-02T23:11:16 1990-03-02T23:11:39 ... * y (y) float64 -3.919e+06 -3.919e+06 -3.919e+06 -3.919e+06 ... * x (x) float64 1.538e+06 1.538e+06 1.538e+06 1.538e+06 1.538e+06 ...

There is a check to make sure the data is not remote, but not based on dask status, see: https://github.com/pydata/xarray/blob/master/xarray/core/formatting.py#L173 Is there a way to indicate that computing a particular dask is an expensive operation and it should not be calculated?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/820/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
257643746 MDExOlB1bGxSZXF1ZXN0MTQxMDE3NTcw 1573 DOC: Update broken link to dask blog post andrewdhicks 15901813 closed 0     1 2017-09-14T08:56:27Z 2017-09-14T17:04:22Z 2017-09-14T17:04:21Z NONE   0 pydata/xarray/pulls/1573 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1573/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]);