home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

7 rows where user = 193170 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 4

  • `Dataset.to_zarr` compute=False should allow access to awaitable 3
  • Question: Feature request: test isolation and storage engine cache 2
  • Reading and writing a zarr dataset multiple times casts bools to int8 1
  • Writing np.bool8 data array reads in as int8 1

user 1

  • shaunc · 7 ✖

author_association 1

  • NONE 7
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
1073389475 https://github.com/pydata/xarray/issues/6383#issuecomment-1073389475 https://api.github.com/repos/pydata/xarray/issues/6383 IC_kwDOAMm_X84_-p-j shaunc 193170 2022-03-21T00:47:45Z 2022-03-21T00:47:45Z NONE

You can return a awaitable explicitly without declaring async. I'm not sure what the best style is -- if there is no await then asyncio will issue a warning in debug mode. Perhaps you can mark it ... Alternately, you could pass in an event loop to computed=, which would trigger the task being added with create_task() (as well as being returned?)

As for a contribution ... I'm already hacking on something but it isn't pretty. Will need to think more about how to do it the right way.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  `Dataset.to_zarr` compute=False should allow access to awaitable 1174427142
1073313461 https://github.com/pydata/xarray/issues/6383#issuecomment-1073313461 https://api.github.com/repos/pydata/xarray/issues/6383 IC_kwDOAMm_X84_-Xa1 shaunc 193170 2022-03-20T19:07:56Z 2022-03-20T19:07:56Z NONE

to_zarr could return a task if compute=False even without being async. zarr depends on fsspec depends of s3fs which is async. I think you can get an awaitable from fsspec. I'm not sure about zarr, but looks like you can pass your own store -- which may be the way to do it.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  `Dataset.to_zarr` compute=False should allow access to awaitable 1174427142
1073159748 https://github.com/pydata/xarray/issues/6383#issuecomment-1073159748 https://api.github.com/repos/pydata/xarray/issues/6383 IC_kwDOAMm_X84_9x5E shaunc 193170 2022-03-20T03:41:57Z 2022-03-20T03:42:14Z NONE

Hmm... probably I should be filing a feature request for this rather than a bug.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  `Dataset.to_zarr` compute=False should allow access to awaitable 1174427142
822981416 https://github.com/pydata/xarray/issues/4826#issuecomment-822981416 https://api.github.com/repos/pydata/xarray/issues/4826 MDEyOklzc3VlQ29tbWVudDgyMjk4MTQxNg== shaunc 193170 2021-04-20T05:21:40Z 2021-04-20T05:22:29Z NONE

Closed https://github.com/pydata/xarray/issues/5192 in favor of this as I think it's a duplicate. Just NB that it can occur with h5netcdf as well as netcdf4. (Thanks, @andersy005 )

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Reading and writing a zarr dataset multiple times casts bools to int8 789410367
822980762 https://github.com/pydata/xarray/issues/5192#issuecomment-822980762 https://api.github.com/repos/pydata/xarray/issues/5192 MDEyOklzc3VlQ29tbWVudDgyMjk4MDc2Mg== shaunc 193170 2021-04-20T05:19:44Z 2021-04-20T05:19:44Z NONE

Aha -- I think that is exactly it. I'll close in favor of that (just noting though that h5netcdf also has the problem).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Writing np.bool8 data array reads in as int8 862110000

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