home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER" and issue = 654678508 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

  • dcherian 2
  • TomNicholas 1

issue 1

  • Add initial cupy tests · 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
657616206 https://github.com/pydata/xarray/pull/4214#issuecomment-657616206 https://api.github.com/repos/pydata/xarray/issues/4214 MDEyOklzc3VlQ29tbWVudDY1NzYxNjIwNg== dcherian 2448579 2020-07-13T15:07:38Z 2020-07-13T15:07:38Z MEMBER

I'm merging so that @jacobtomlinson can keep moving forward.

It isn't breaking anything too :)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add initial cupy tests 654678508
656725555 https://github.com/pydata/xarray/pull/4214#issuecomment-656725555 https://api.github.com/repos/pydata/xarray/issues/4214 MDEyOklzc3VlQ29tbWVudDY1NjcyNTU1NQ== dcherian 2448579 2020-07-10T15:09:07Z 2020-07-10T15:09:07Z MEMBER

run a nightly against the default branch on some GPU hardware. If the nightly fails we will open an issue and look into resolving it.

This is great! Thanks @jacobtomlinson

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add initial cupy tests 654678508
656608745 https://github.com/pydata/xarray/pull/4214#issuecomment-656608745 https://api.github.com/repos/pydata/xarray/issues/4214 MDEyOklzc3VlQ29tbWVudDY1NjYwODc0NQ== TomNicholas 35968931 2020-07-10T10:37:53Z 2020-07-10T10:37:53Z MEMBER

Hi Jacob, would it make sense to add a new CI job that has cupy so that these tests actually get run automatically on future PRs? At the moment they're just going to get skipped, but if you're planning to work on this it might be a good idea to automate the cupy integration tests early on?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add initial cupy tests 654678508

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