home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 370960004 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 3

  • shoyer 1
  • benbovy 1
  • stale[bot] 1

author_association 2

  • MEMBER 2
  • NONE 1

issue 1

  • Renaming a coordinate of a multi-index after stack fails · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
919888916 https://github.com/pydata/xarray/issues/2489#issuecomment-919888916 https://api.github.com/repos/pydata/xarray/issues/2489 IC_kwDOAMm_X8421GQU benbovy 4160723 2021-09-15T10:15:37Z 2021-09-15T10:15:37Z MEMBER

This should be fixed in #5692 now.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Renaming a coordinate of a multi-index after stack fails 370960004
695343999 https://github.com/pydata/xarray/issues/2489#issuecomment-695343999 https://api.github.com/repos/pydata/xarray/issues/2489 MDEyOklzc3VlQ29tbWVudDY5NTM0Mzk5OQ== stale[bot] 26384082 2020-09-19T18:52:07Z 2020-09-19T18:52:07Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Renaming a coordinate of a multi-index after stack fails 370960004
431097096 https://github.com/pydata/xarray/issues/2489#issuecomment-431097096 https://api.github.com/repos/pydata/xarray/issues/2489 MDEyOklzc3VlQ29tbWVudDQzMTA5NzA5Ng== shoyer 1217238 2018-10-18T17:35:46Z 2018-10-18T17:35:46Z MEMBER

MultiIndex levels should really be xarray.Variable objects, but unfortunately that isn't the case right now. We have some special cases in indexing to dynamically create xarray.Variable objects, but it isn't done consistently in all functions.

The refactor envisioned in https://github.com/pydata/xarray/issues/1603 should eventually fix this.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Renaming a coordinate of a multi-index after stack fails 370960004

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);
Powered by Datasette · Queries took 561.047ms · About: xarray-datasette