home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where issue = 668166816 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

  • keewis 2
  • dopplershift 1
  • crusaderky 1

author_association 2

  • MEMBER 3
  • CONTRIBUTOR 1

issue 1

  • failing docs CI · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
667583607 https://github.com/pydata/xarray/issues/4287#issuecomment-667583607 https://api.github.com/repos/pydata/xarray/issues/4287 MDEyOklzc3VlQ29tbWVudDY2NzU4MzYwNw== crusaderky 6213168 2020-08-01T20:31:36Z 2020-08-01T20:31:36Z MEMBER

Temporarily pinning pandas=1.0 in https://github.com/pydata/xarray/pull/4296

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  failing docs CI 668166816
666789182 https://github.com/pydata/xarray/issues/4287#issuecomment-666789182 https://api.github.com/repos/pydata/xarray/issues/4287 MDEyOklzc3VlQ29tbWVudDY2Njc4OTE4Mg== keewis 14808389 2020-07-30T23:54:56Z 2020-07-30T23:54:56Z MEMBER

thanks, @dopplershift, the exception does indeed look like #4283.

The warnings are a sphinx bug (see sphinx-doc/sphinx#7799), but it will probably take some time until the release of sphinx 3.2.0. I guess that means we have to live with these warnings until then? We could use suppress_warnings, but that would ignore all warnings about invalid formatting.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  failing docs CI 668166816
666714053 https://github.com/pydata/xarray/issues/4287#issuecomment-666714053 https://api.github.com/repos/pydata/xarray/issues/4287 MDEyOklzc3VlQ29tbWVudDY2NjcxNDA1Mw== dopplershift 221526 2020-07-30T21:27:14Z 2020-07-30T21:27:14Z CONTRIBUTOR

The exception looks like the identical problem as #4283 .

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  failing docs CI 668166816
666318397 https://github.com/pydata/xarray/issues/4287#issuecomment-666318397 https://api.github.com/repos/pydata/xarray/issues/4287 MDEyOklzc3VlQ29tbWVudDY2NjMxODM5Nw== keewis 14808389 2020-07-30T11:49:52Z 2020-07-30T11:49:52Z MEMBER

I can confirm that downgrading fixes the build. Not sure what changed, but we should try to extend our plotting tests so we can catch this using the upstream-dev CI.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  failing docs CI 668166816

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 15.534ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows