home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER", issue = 735523592 and user = 10194086 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • mathause · 3 ✖

issue 1

  • Cannot plot multiindexed (stacked) coordinate as hue variable · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
729275558 https://github.com/pydata/xarray/issues/4562#issuecomment-729275558 https://api.github.com/repos/pydata/xarray/issues/4562 MDEyOklzc3VlQ29tbWVudDcyOTI3NTU1OA== mathause 10194086 2020-11-17T23:27:47Z 2020-11-17T23:27:47Z MEMBER

You have to specify x as well: da.plot(hue='mi_idx1', x="x"). But yes, this is not ideal - would be nice to get this working with hue="mi".

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Cannot plot multiindexed (stacked) coordinate as hue variable  735523592
721855875 https://github.com/pydata/xarray/issues/4562#issuecomment-721855875 https://api.github.com/repos/pydata/xarray/issues/4562 MDEyOklzc3VlQ29tbWVudDcyMTg1NTg3NQ== mathause 10194086 2020-11-04T17:04:28Z 2020-11-04T17:04:28Z MEMBER

Yes seems a sems like a sensible approach. Maybe you can use hue="mi_idx1" and set the label manually as a workaround. (Can't test right now)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Cannot plot multiindexed (stacked) coordinate as hue variable  735523592
721348538 https://github.com/pydata/xarray/issues/4562#issuecomment-721348538 https://api.github.com/repos/pydata/xarray/issues/4562 MDEyOklzc3VlQ29tbWVudDcyMTM0ODUzOA== mathause 10194086 2020-11-03T20:06:33Z 2020-11-03T20:06:33Z MEMBER

That might be my doing here: #3938 It makes sense to allow a MultiIndex as a label but probably not as a coordinate. So this may need some thinking.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Cannot plot multiindexed (stacked) coordinate as hue variable  735523592

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 3687.401ms · About: xarray-datasette