home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER", issue = 778069594 and user = 14808389 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

  • keewis · 3 ✖

issue 1

  • WIP: testing.assert_* check dtype · 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
774106999 https://github.com/pydata/xarray/pull/4760#issuecomment-774106999 https://api.github.com/repos/pydata/xarray/issues/4760 MDEyOklzc3VlQ29tbWVudDc3NDEwNjk5OQ== keewis 14808389 2021-02-05T15:35:18Z 2021-02-05T16:00:17Z MEMBER

to really fix this we need some way to say "I really want to convert to a numpy.ndarray" (unfortunately, np.asarray seems to be commonly used as "ensure that this is a numpy.ndarray"). That's the same issue as with cupy.Array, which will raise in __array__.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: testing.assert_* check dtype 778069594
774115528 https://github.com/pydata/xarray/pull/4760#issuecomment-774115528 https://api.github.com/repos/pydata/xarray/issues/4760 MDEyOklzc3VlQ29tbWVudDc3NDExNTUyOA== keewis 14808389 2021-02-05T15:49:32Z 2021-02-05T15:59:52Z MEMBER

yes, I agree that it makes sense to set warnings to "always" in the assert_* functions.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: testing.assert_* check dtype 778069594
774024142 https://github.com/pydata/xarray/pull/4760#issuecomment-774024142 https://api.github.com/repos/pydata/xarray/issues/4760 MDEyOklzc3VlQ29tbWVudDc3NDAyNDE0Mg== keewis 14808389 2021-02-05T13:10:27Z 2021-02-05T14:14:20Z MEMBER

the difference is that the unit registry has force_ndarray_like enabled. This is important because a pint.Quantity wrapping a python scalar is not a duck array, so the unit gets stripped.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: testing.assert_* check dtype 778069594

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