issues
5 rows where state = "closed", type = "issue" and user = 2818208 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: comments, created_at (date), updated_at (date), closed_at (date)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
499937876 | MDU6SXNzdWU0OTk5Mzc4NzY= | 3355 | Define aligning, broadcasting, merging, concatenating, combining in new glossary | gwgundersen 2818208 | closed | 0 | 1 | 2019-09-29T16:16:45Z | 2023-08-18T19:49:00Z | 2023-08-18T19:49:00Z | CONTRIBUTOR | Over at https://github.com/pydata/xarray/pull/3352, we're working on a new page describing key Xarray terminology for https://github.com/pydata/xarray/issues/2410. Since it's already a big PR, and we may need to iterate on the definitions a few times, this issue is for extending the glossary once that PR is merged. Some terms are to add are: aligning, broadcasting, merging, concatenating, combining. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3355/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
482452409 | MDU6SXNzdWU0ODI0NTI0MDk= | 3231 | Dict-like argument support for assign_coords() | gwgundersen 2818208 | closed | 0 | 3 | 2019-08-19T18:07:39Z | 2019-09-28T20:44:08Z | 2019-09-28T20:44:08Z | CONTRIBUTOR | Often the xarray API supports either a ```python
Since ```python
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3231/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
482023929 | MDU6SXNzdWU0ODIwMjM5Mjk= | 3227 | Building the docs creates temporary files | gwgundersen 2818208 | closed | 0 | 7 | 2019-08-18T18:38:06Z | 2019-08-28T00:02:02Z | 2019-08-28T00:02:02Z | CONTRIBUTOR | MCVEApologies if this has already been noted, but I can't find an open issue. When I create the docs from scratch, I see a couple temporary files and directories that appear to have been created by accident. If this is a legitimate issue, I'm happy to put together a PR. Here is an MCVE: ```bash (xarray-docs) gwg:doc gwg$ make clean rm -rf _build/ rm -rf generated/ rm -rf auto_gallery/ (xarray-docs) gwg:doc gwg$ git status On branch master Your branch is up to date with 'origin/master'. nothing to commit, working tree clean (xarray-docs) gwg:doc gwg$ make html sphinx-build -b html -d _build/doctrees . _build/html' ... Build finished. The HTML pages are in _build/html. (xarray-docs) gwg:doc gwg$ git status On branch master Your branch is up to date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed)
nothing added to commit but untracked files present (use "git add" to track) ``` Expected OutputI would expect no files to be created by Problem DescriptionIt's not clear this will happen and may result in some people (me!) accidentally committing these files with |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3227/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
484089737 | MDU6SXNzdWU0ODQwODk3Mzc= | 3240 | assign_coords adds coordinates without a new dimension if the value is scalar | gwgundersen 2818208 | closed | 0 | 5 | 2019-08-22T16:14:05Z | 2019-08-26T08:16:37Z | 2019-08-26T08:16:37Z | CONTRIBUTOR | Problem
MCVEConsider the following ```python
I can assign new coordinates to an existing dimension: ```python
And I cannot (correctly) assign coordinates to a new (nonexistent) dimension: ```python
The above fails because Xarray, in the absence of an explicit dimension, tries to assign the new coordinates to a ```python
I would expect this to fail because ```python
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3240/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
476103888 | MDU6SXNzdWU0NzYxMDM4ODg= | 3176 | DataArray.set_index throws error on documented input | gwgundersen 2818208 | closed | 0 | 7 | 2019-08-02T10:09:04Z | 2019-08-19T16:02:53Z | 2019-08-19T16:02:53Z | CONTRIBUTOR | Problem DescriptionDocs for
This suggests that one can set a MCVE```python In [1]: import numpy as np In [2]: import xarray as xr In [3]: arr = xr.DataArray(data=np.ones((2, 3)), dims=['x', 'y']) In [4]: arr.dims Out[4]: ('x', 'y') In [5]: arr.set_index({'x': range(2)})
KeyError KeyError: 0 ``` At first, I thought it might be because ```python In [18]: arr.coords Out[18]: Coordinates: empty In [19]: arr._coords Out[19]: OrderedDict() ``` but even if I set the coordinates first and then try to re-index, it fails:
Expected OutputI expect my MCVE to work based on the documentation. Problem SolutionMy guess is that the issue is Xarray is using the |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3176/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
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]);