issues

Table actions

4 rows where repo = 13221727, type = "pull" and user = 4414299 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 1

  • pull · 4 ✖

state 1

repo 1

  • xarray · 4 ✖
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
271045071 MDExOlB1bGxSZXF1ZXN0MTUwNTc3MTU1 1690 Add names for test failures maaleske 4414299 closed 0     3 2017-11-03T16:48:16Z 2020-06-13T17:53:03Z 2020-06-13T17:53:03Z CONTRIBUTOR   0 pydata/xarray/pulls/1690

This PR adds the coordinate name to the test failure printout in assert_allclose() when cycling through the coordinates . Specifying the coordinate makes test failures much easier to diagnose just based on the message.

  • [ ] Closes #xxxx
  • [x] Tests added / passed
  • [x] Passes git diff upstream/master **/*py | flake8 --diff
  • [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/1690/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
359449421 MDExOlB1bGxSZXF1ZXN0MjE0OTM2NzI3 2413 Allow passing of positional arguments in `apply` for Groupby objects maaleske 4414299 closed 0     8 2018-09-12T12:06:13Z 2018-12-24T17:50:29Z 2018-12-24T17:50:20Z CONTRIBUTOR   0 pydata/xarray/pulls/2413
  • [x] Closes #2412
  • [x] Tests added (for all bug fixes or enhancements)
  • [x] Tests passed (for all non-documentation changes)
  • [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/2413/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
259058863 MDExOlB1bGxSZXF1ZXN0MTQyMDIzMjIx 1583 Parsing wavelength info from rasterio tags maaleske 4414299 closed 0     4 2017-09-20T06:57:16Z 2017-12-12T14:38:59Z 2017-12-12T14:38:53Z CONTRIBUTOR   0 pydata/xarray/pulls/1583

Proof of concept for reading info from rasterio tags() in open_rasterio. Not quite a solution to #1582, but possibly workable to a more general solution.

Currently implements the following: - Reads tags(band_idx) for each band and extracts the wavelength values from the result dictionaries as a coordinate for the returned DataArray. - Reads the wavelength_units from tags(1) and sets it as an attribute (assumes it's the same for each band, which it is for ENVI format files)

  • [x] Closes #1582 (Maybe?)
  • [x] Tests added / passed
  • [x] Passes git diff upstream/master | flake8 --diff
  • [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/1583/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
271017521 MDExOlB1bGxSZXF1ZXN0MTUwNTU2NjI4 1687 Remove netCDF dependency from rasterio backend tests maaleske 4414299 closed 0     7 2017-11-03T15:26:44Z 2017-11-05T22:09:02Z 2017-11-05T19:42:33Z CONTRIBUTOR   0 pydata/xarray/pulls/1687

The rasterio backend tests each currently have a netcdf roundtrip test without the appropriate requires_scipy_or_netCDF4 decorator, which causes them to always fail when ran without either. They also do not seem to be necessary for testing the rasterio backend functionality, and just add an extra dependency to the tests. The netCDF roundtrip also seems to be already better tested by the other tests in the same file.

  • [x] Tests added / passed
  • [x] Passes git diff upstream/master **/*py | flake8 --diff
  • [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/1687/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]);