home / github

Menu
  • GraphQL API
  • Search all tables

issues

Table actions
  • GraphQL API for issues

2 rows where user = 1020496 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
746549764 MDExOlB1bGxSZXF1ZXN0NTIzOTIzNDcx 4594 BUG: fix the CSS for dt / dd to only apply to xarray repr jorisvandenbossche 1020496 closed 0     3 2020-11-19T12:40:41Z 2020-11-20T20:35:22Z 2020-11-20T20:24:54Z MEMBER   0 pydata/xarray/pulls/4594

xref https://github.com/pandas-dev/pydata-sphinx-theme/issues/284

The current CSS had the consequence that those rules were applied to all <dd> elements, and not only the ones with the xr-attrs class. I don't know if there is a smarter way in CSS to select two element types using the class rather than repeating the class name as I did here, but this works.

cc @benbovy

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4594/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    xarray 13221727 pull
462181094 MDU6SXNzdWU0NjIxODEwOTQ= 3057 Remove remaining usage of pandas Panel jorisvandenbossche 1020496 closed 0     1 2019-06-28T19:40:15Z 2019-06-30T18:01:07Z 2019-06-30T18:01:07Z MEMBER      

There is still some usage of pd.Panel (just accessing the name in the pandas namespace for isinstance check), eg:

https://github.com/pydata/xarray/blob/a78e0f6ce7c0cc48f746a122c79f1bcf903efd51/xarray/core/merge.py#L18

We are currently removing Panel from pandas (https://github.com/pandas-dev/pandas/pull/27101), so that breaks xarray (and statsmodels). For that reason, we are going to keep an empty class so that the above use case doesn't directly break. But it would still be good to remove that usage (or only add it for pandas versions below 0.25.0)

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