issues

Table actions

5 rows where user = 35924738 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 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
2070189273 I_kwDOAMm_X857ZJTZ 8596 Updated `See also` section in the docstrings broke numpydoc maximlt 35924738 open 0     0 2024-01-08T10:47:36Z 2024-01-09T19:24:39Z   CONTRIBUTOR      

What happened?

Hi, I would like to report that https://github.com/pydata/xarray/pull/8311 broke the documentation build of Datashader. Datashader's documentation uses Sphinx and numpydoc to process its docstrings. It turns out (I had no idea) that numpydoc processes more doctrings than I'd have expected, including xarray's ones. The changes in the PR made numpydoc unhappy. To reproduce run:

python3 -m venv .venv source .venv/bin/activate pip install numpydoc python -m numpydoc.hooks.validate_docstrings xarray/core/dataarray.py

You'll get this error:

ValueError: Error parsing See Also entry ':doc:`xarray-tutorial:intermediate/indexing/indexing`'

I'm pretty sure this is not an xarray issue but felt that opening an issue here might be useful for others encountering this issue. Really, feel free to close it.

What did you expect to happen?

No response

Minimal Complete Verifiable Example

No response

MVCE confirmation

  • [ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
  • [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
  • [ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
  • [ ] New issue — a search of GitHub Issues suggests this is not a duplicate.
  • [ ] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output

No response

Anything else we need to know?

No response

Environment

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8596/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 issue
995207963 MDU6SXNzdWU5OTUyMDc5NjM= 5791 Histogram's plot title could include the scalar coords values instead of being set to `Histogram` maximlt 35924738 closed 0     0 2021-09-13T18:42:38Z 2021-09-29T16:03:26Z 2021-09-29T16:03:26Z CONTRIBUTOR      

The plots created by xarray.plot() often include an informative title that lists the scalar coords and their values. The histogram plot doesn't have that feature, it gets a title called Histogram. It would be nice to have this plot to also benefit from an informative title.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5791/reactions",
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
995217866 MDExOlB1bGxSZXF1ZXN0NzMzMDEzMzI4 5792 Set scalar coords title to histogram plots maximlt 35924738 closed 0     4 2021-09-13T18:56:14Z 2021-09-29T16:03:26Z 2021-09-29T16:03:26Z CONTRIBUTOR   0 pydata/xarray/pulls/5792

Closes #5791

If the feature request is accepted :)

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5792/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
995202695 MDExOlB1bGxSZXF1ZXN0NzMzMDAwOTA1 5789 fix float formatting in a plot's title maximlt 35924738 closed 0     2 2021-09-13T18:35:36Z 2021-09-23T18:31:22Z 2021-09-23T18:28:50Z CONTRIBUTOR   0 pydata/xarray/pulls/5789

Closes #5788 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5789/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
995189423 MDU6SXNzdWU5OTUxODk0MjM= 5788 Numeric numbers not properly formatted in the title's plot maximlt 35924738 closed 0     0 2021-09-13T18:18:59Z 2021-09-23T18:28:50Z 2021-09-23T18:28:50Z CONTRIBUTOR      

See one of the figures generated in the ROMS tutorial where Cs_r is displayed in a very long format.

Observed in the work done in here: https://github.com/holoviz/hvplot/pull/659

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