home / github

Menu
  • GraphQL API
  • Search all tables

issues

Table actions
  • GraphQL API for issues

2 rows where state = "closed" and user = 1228240 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 1

  • issue 2

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
131972229 MDU6SXNzdWUxMzE5NzIyMjk= 748 IO fails with complex datatypes arsenovic 1228240 closed 0     8 2016-02-07T14:34:10Z 2019-02-24T13:25:39Z 2019-02-24T13:25:39Z NONE      

i am exploring the use of xarray as a back-end for some objects in the scikit-rf project. this, and other electrical engineering applications require support for complex data-types. - is there a [non-pickle] serialization that works with this? - i dont get an error but it seems to loose the data?

https://gist.github.com/613be985bcf0001ebd05

( i have xarray 0.7.0)

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/748/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed xarray 13221727 issue
131386008 MDU6SXNzdWUxMzEzODYwMDg= 747 unit support? arsenovic 1228240 closed 0     2 2016-02-04T15:40:55Z 2016-02-04T15:44:09Z 2016-02-04T15:44:09Z NONE      

i was curious is there is any thoughts to incorperate 'units' with xarray?

pint is a package that implements this.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/747/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 20.86ms · About: xarray-datasette