home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

5 rows where user = 1228240 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 4

  • IO fails with complex datatypes 2
  • support for units 1
  • unit support? 1
  • A suggested solution to the `TypeError: Invalid value for attr:` error upon `.to_netcdf` 1

user 1

  • arsenovic · 5 ✖

author_association 1

  • NONE 5
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1194287221 https://github.com/pydata/xarray/issues/3743#issuecomment-1194287221 https://api.github.com/repos/pydata/xarray/issues/3743 IC_kwDOAMm_X85HL2B1 arsenovic 1228240 2022-07-25T16:02:27Z 2022-07-25T17:22:41Z NONE

would be nice better to wrap it and make it round trippable (especially for simple things like None )

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  A suggested solution to the `TypeError: Invalid value for attr:` error upon `.to_netcdf` 558977158
182947295 https://github.com/pydata/xarray/issues/748#issuecomment-182947295 https://api.github.com/repos/pydata/xarray/issues/748 MDEyOklzc3VlQ29tbWVudDE4Mjk0NzI5NQ== arsenovic 1228240 2016-02-11T16:38:04Z 2016-02-11T16:38:04Z NONE

excellent. thanks for looking into it, this work around is sufficient for my needs fyi.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  IO fails with complex datatypes 131972229
181944878 https://github.com/pydata/xarray/issues/525#issuecomment-181944878 https://api.github.com/repos/pydata/xarray/issues/525 MDEyOklzc3VlQ29tbWVudDE4MTk0NDg3OA== arsenovic 1228240 2016-02-09T16:32:32Z 2016-02-09T16:32:32Z NONE

id just like to chime in and say that this feature would really be sweet. i always find myself doing a lot work to handle/convert different units. it seems that adding units to labeled axes does a lot to describe a set of data.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  support for units 100295585
181490631 https://github.com/pydata/xarray/issues/748#issuecomment-181490631 https://api.github.com/repos/pydata/xarray/issues/748 MDEyOklzc3VlQ29tbWVudDE4MTQ5MDYzMQ== arsenovic 1228240 2016-02-08T17:36:51Z 2016-02-08T17:36:51Z NONE

2.5.0-np19py27_3 from conda

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  IO fails with complex datatypes 131972229
179906290 https://github.com/pydata/xarray/issues/747#issuecomment-179906290 https://api.github.com/repos/pydata/xarray/issues/747 MDEyOklzc3VlQ29tbWVudDE3OTkwNjI5MA== arsenovic 1228240 2016-02-04T15:42:12Z 2016-02-04T15:42:22Z NONE

@hgrecco, might have thoughts on this

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  unit support? 131386008

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