issues

Table actions

5 rows where state = "closed" and user = 17169544 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)

type 2

state 1

  • closed · 5 ✖

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
467764970 MDExOlB1bGxSZXF1ZXN0Mjk3MzQ2NzYz 3113 [DOC] Be more explicit about netCDF groups and xarray.Dataset relationship. zdgriffith 17169544 closed 0     1 2019-07-13T20:48:58Z 2019-07-14T05:34:56Z 2019-07-14T05:34:56Z CONTRIBUTOR   0 pydata/xarray/pulls/3113

This PR is related to the discussion in #2916. In https://xarray.pydata.org/en/stable/io.html#netcdf there are statements like

netCDF files on disk directly correspond to Dataset objects.

This is useful conceptually but can be confusing when working with netCDF groups which are not supported as part of the data model. I thought it would be clearer if the description of how to work with groups explicitly said this.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3113/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
467741491 MDExOlB1bGxSZXF1ZXN0Mjk3MzMwMTA3 3110 Change name of testing conda environment zdgriffith 17169544 closed 0     5 2019-07-13T16:41:09Z 2019-07-13T17:12:30Z 2019-07-13T17:11:52Z CONTRIBUTOR   0 pydata/xarray/pulls/3110

This PR changes the test environment name from test_env to xarray-tests for clarity and to be consistent with the documentation environment name (xarray-docs).

  • [x] Closes #3107 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3110/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
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
444510710 MDExOlB1bGxSZXF1ZXN0Mjc5MTU2MDI1 2964 Add fill_value for concat and auto_combine zdgriffith 17169544 closed 0     7 2019-05-15T15:40:48Z 2019-05-27T00:21:02Z 2019-05-27T00:20:55Z CONTRIBUTOR   0 pydata/xarray/pulls/2964

This PR adds the optional fill_value parameter to concat() and auto_combine() in xarray.core.combine, plus the associated underlying functions in the module. This builds on the previous PR #2920 in addressing issue #2876, and gives users the option to avoid type-changing to float for arrays with missing values when using these functions as discussed in issue #2870.

  • [x] Closes #2870
  • [x] Tests added
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2964/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
437418337 MDExOlB1bGxSZXF1ZXN0MjczNjk5NjUz 2920 [WIP] Custom fill value for reindex, align, and merge operations zdgriffith 17169544 closed 0     5 2019-04-25T22:08:09Z 2019-05-05T20:31:58Z 2019-05-05T00:20:55Z CONTRIBUTOR   0 pydata/xarray/pulls/2920

This PR adds an optional fill_value parameter for the following functions/methods: ``` xarray.core.alignment.align() xarray.core.alignment.deep_align()

xarray.core.dataset.reindex() xarray.core.dataset.reindex_like() xarray.core.dataset.merge()

xarray.core.dataarray.DataArray.reindex() xarray.core.dataarray.DataArray.reindex_like()

xarray.core.merge.merge_coords() xarray.core.merge.merge_core() xarray.core.merge.merge() xarray.core.merge.dataset_merge_method() `` The value given tofill_valueis used to fill missing values in the new object after the operation. By defaultfill_value` is NaN.

  • [x] Closes #2876
  • [x] Tests added
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2920/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]);