home / github

Menu
  • GraphQL API
  • Search all tables

issues

Table actions
  • GraphQL API for issues

2 rows where user = 4194485 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 2

  • issue 1
  • pull 1

state 1

  • closed 2

repo 1

  • xarray 2
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
49478188 MDU6SXNzdWU0OTQ3ODE4OA== 279 BUG: reindex method creates new dims/coords ToddSmall 4194485 closed 0   0.3.2 836999 0 2014-11-20T01:29:21Z 2014-12-19T07:21:31Z 2014-12-19T07:21:31Z NONE      

If you reindex an xray dataset or dataarray with a coordinate with a different name, an extra dimension and coordinate is added to the xray object (with the name of the reindexing coordinate). Here's a simple example:

x1 = xray.DataArray(np.random.randn(5, 6, 7), dims=["lon", "lat", "time"]) time2 = xray.DataArray([1, 3], dims="time2") x2 = x1.reindex(time=time2)

x2 now has coordinates "time" and "time2".

I'm using xray version 0.3.1-4-gee1369f.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/279/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed xarray 13221727 issue
35760380 MDExOlB1bGxSZXF1ZXN0MTcxNTcyMjI= 162 Change np.isnan to pd.isnull in conventions.py to handle _FillValue = '' ToddSmall 4194485 closed 0     1 2014-06-15T23:10:29Z 2014-06-15T23:16:48Z 2014-06-15T23:16:35Z NONE   0 pydata/xarray/pulls/162

At a number of spots in conventions.py, np.isnan was being used to check possible fill values. However, np.isnan is not implemented for string types. So, I've replaced np.isnan with pd.isnull.

Alas, I haven't been able to update the tests to cover _FillValue = '', because doing so would involve significant changes throughout the code base.

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