home / github

Menu
  • GraphQL API
  • Search all tables

issues

Table actions
  • GraphQL API for issues

3 rows where type = "issue" and user = 7213793 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)

state 2

  • closed 2
  • open 1

type 1

  • issue · 3 ✖

repo 1

  • xarray 3
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
892812331 MDU6SXNzdWU4OTI4MTIzMzE= 5320 Confused about variable declared but not used in DataArray documentation canyon289 7213793 closed 0     1 2021-05-17T01:27:08Z 2021-05-17T03:52:37Z 2021-05-17T03:52:37Z CONTRIBUTOR      

The documentation for xr.DataArray includes this precipitation variable but it doesnt actually seem to be used anywhere? Was it intended to showcase some functionality or is it superfluous?

If its not needed can it be removed? Whatever the fix is I'm happy to make a PR (if not im not mistaken!) http://xarray.pydata.org/en/stable/generated/xarray.DataArray.html#xarray.DataArray

Edit I see it is used in Dataset documentation so now get the intent. I still suggest removing it from xr.DataArray as its not used there. http://xarray.pydata.org/en/stable/user-guide/data-structures.html

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5320/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed xarray 13221727 issue
563762277 MDU6SXNzdWU1NjM3NjIyNzc= 3765 ArviZ Dev Xarray Dev Get Together? canyon289 7213793 open 0     23 2020-02-12T05:25:43Z 2020-03-27T17:50:09Z   CONTRIBUTOR      

Hi Xarray folks

I work on ArviZ and am the guy behind this tweet. https://twitter.com/arviz_devs/status/1225998959161663488

We use xarray heavily in ArviZ, its our central data object. We have questions about the current api and plans for the future api, and a number of our core developers were wondering you guys wanted to get together sometime, perhaps at one of the popular conferences like scipy, or probprog, or something like that.

In the meanwhile we've been collecting examples for things we can create reproducible examples for, but are hoping to chat at a higher level as well. https://github.com/arviz-devs/xarray_examples

Let us know if this sounds interesting. Thanks for all the hard work on xarray

cc @rpgoldman @aloctavodia @OriolAbril @ahartikainen

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3765/reactions",
    "total_count": 2,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 2,
    "rocket": 0,
    "eyes": 0
}
    xarray 13221727 issue
362854704 MDU6SXNzdWUzNjI4NTQ3MDQ= 2429 Documentation Review Request for Arviz canyon289 7213793 closed 0     7 2018-09-22T12:49:11Z 2018-09-29T03:51:07Z 2018-09-27T04:05:47Z CONTRIBUTOR      

Hello, This isn't an issue with Xarray, I just wasn't sure of how to generally contact the Xarray devs other than a github Issue.

Arviz would like to add some light documentation to introduce our users to xarray. We wanted to reach out to see if xarray devs wanted to review it before we "publish" it to our docs.

There's no obligation of course, we just wanted to ensure we proactively ask for your feedback if you wanted to provide an opinion.

Notebook https://github.com/arviz-devs/arviz/blob/2b95e70dce7cf4f3c1bc41bcc030b1bf1b579359/doc/notebooks/XarrayforArviZ.ipynb

Pull request https://github.com/arviz-devs/arviz/pull/256

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2429/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]);
Powered by Datasette · Queries took 21.409ms · About: xarray-datasette