issues

Table actions

4 rows where repo = 13221727 and user = 13667821 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: comments, updated_at, closed_at, created_at (date), updated_at (date), closed_at (date)

type 2

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
485390288 MDU6SXNzdWU0ODUzOTAyODg= 3264 Clarify documentation of argmin/argmax rdrussotto 13667821 closed 0     5 2019-08-26T18:57:42Z 2020-08-18T17:57:43Z 2020-08-18T17:57:43Z CONTRIBUTOR      

The documentation pages only refer to argmin/argmax without defining them (e.g. "Returns: New DataArray object with argmin applied to its data"), forcing users to refer to the NumPy documentation to learn what the functions do do and try to guess at how the XArray version will work. I think the doc pages should say what these functions actually do, possibly with an example of a common use case, e.g. finding the latitude where some quantity is minimized.

Also, the first time I used argmin/argmax I wasn't sure from the documentation whether the returned value is the coordinate index or the raw index. I think this should be explicitly stated. I also like the idea mentioned in issue #1388 of creating an alternate version of argmin/argmax that does return the coordinate index, since it would make it easier to stay within the coordinate indices all the time. 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3264/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
552026801 MDU6SXNzdWU1NTIwMjY4MDE= 3708 Broken Sphinx links in doc page on contributing to docs rdrussotto 13667821 closed 0     5 2020-01-20T01:56:53Z 2020-01-26T17:32:45Z 2020-01-26T17:32:45Z CONTRIBUTOR      

The doc page on contributing to the docs has two broken links to sphinx.pocoo.org. The content has been moved to sphinx-doc.org. The doc page should be updated to reflect this.

Also, it would be useful to explicitly specify that you need to install sphinx, nbsphinx, and all the nbsphinx prerequesites in order to build the docs, as well as installing any additional missing packages that cause errors during the doc build process (I had to install cfgrib and h5netcdf).

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3708/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
552577668 MDExOlB1bGxSZXF1ZXN0MzY1MDU3NTg0 3710 Fix Sphinx links on contributing doc page rdrussotto 13667821 closed 0     2 2020-01-21T01:33:44Z 2020-01-26T17:32:45Z 2020-01-26T17:32:45Z CONTRIBUTOR   0 pydata/xarray/pulls/3710
  • [ ] Closes #3708

The links to the main Sphinx page and the intro to reStructuredText were broken since the pages have been moved from sphinx.pocoo.org to sphinx-doc.org. This PR provides the updated links.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3710/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
467773069 MDExOlB1bGxSZXF1ZXN0Mjk3MzUyMTk0 3119 Clarify apply_ufunc error message (Issue #2078) rdrussotto 13667821 closed 0     9 2019-07-13T22:36:46Z 2019-08-23T18:56:37Z 2019-08-23T18:56:14Z CONTRIBUTOR   0 pydata/xarray/pulls/3119
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API

Changed an error message thrown by a dependent function of apply_ufunc to specify that "an input variable" rather than "the input variable" did not have the correct dimensions. This error occurs when apply_ufunc is used on a Dataset with multiple variables, at least one of which does not have correct dimensions matching the other input arguments. Wanted to add variable name to error message to specify which variable is causing the error, but this isn't possible without significantly refactoring the code. 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3119/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]);