home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where author_association = "NONE", issue = 1517330438 and user = 193170 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

  • shaunc · 2 ✖

issue 1

  • Question: Feature request: test isolation and storage engine cache · 2 ✖

author_association 1

  • NONE · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1370139670 https://github.com/pydata/xarray/issues/7408#issuecomment-1370139670 https://api.github.com/repos/pydata/xarray/issues/7408 IC_kwDOAMm_X85RqqwW shaunc 193170 2023-01-03T19:21:42Z 2023-01-03T19:21:42Z NONE

will do ... as soon as we fix the other bug that doesn't let us get to that step anymore ... :)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Question: Feature request: test isolation and storage engine cache 1517330438
1369880263 https://github.com/pydata/xarray/issues/7408#issuecomment-1369880263 https://api.github.com/repos/pydata/xarray/issues/7408 IC_kwDOAMm_X85RprbH shaunc 193170 2023-01-03T15:10:57Z 2023-01-03T15:10:57Z NONE

We are using s3 and moto - the file itself doesn't exist, as the (fake) bucket is torn down and recreated. The problem is that there is internal state (in zarr?) that references "the old file" even if it actually doesn't exist. We would like to throw out this state on tear-down.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Question: Feature request: test isolation and storage engine cache 1517330438

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