issues

Table actions

2 rows where type = "issue" and user = 17169544 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)

state 2

type 1

  • issue · 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
471409673 MDU6SXNzdWU0NzE0MDk2NzM= 3158 Out of date docstring for concat_dim in open_mfdataset zdgriffith 17169544 open 0     3 2019-07-23T00:01:05Z 2021-07-08T17:40:45Z   CONTRIBUTOR      

In the open_mfdataset docstring:

concat_dim : str, or list of str, DataArray, Index or None, optional Dimensions to concatenate files along. You only need to provide this argument if any of the dimensions along which you want to concatenate is not a dimension in the original datasets, e.g., if you want to stack a collection of 2D arrays along a third dimension. ...

This is true for the default combine='_old_auto', but when using combine='nested' it is required while it is not used by combine='by_coords'. It would be clearer to make that distinction here.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3158/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 issue
467735590 MDU6SXNzdWU0Njc3MzU1OTA= 3107 The name of the conda environment in the contributing guide is generic zdgriffith 17169544 closed 0     3 2019-07-13T15:47:03Z 2019-07-13T17:11:51Z 2019-07-13T17:11:51Z CONTRIBUTOR      

In the contributing guide, you are instructed to make an environment test_env:

```

Create and activate the build environment

conda env create -f ci/requirements/py36.yml conda activate test_env

or with older versions of Anaconda:

source activate test_env

Build and install xarray

pip install -e . ```

I think having the name be xarray_test_env would be clearer for people new to working with conda environments and using multiple projects.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3107/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue

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]);