issue_comments

Table actions

4 rows where issue = 1718410975 and user = 14371165 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

  • Illviljan · 4 ✖

issue 1

  • Unrecognized chunk manager dask - must be one of: [] · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1556198984 https://github.com/pydata/xarray/issues/7856#issuecomment-1556198984 https://api.github.com/repos/pydata/xarray/issues/7856 IC_kwDOAMm_X85cwbZI Illviljan 14371165 2023-05-21T14:51:55Z 2023-05-21T14:51:55Z MEMBER

Nope, I have not tried that. I suspect things will just self heal then considering the CI without understanding the root cause.

Looking at the backends; we initialize a dict here: https://github.com/pydata/xarray/blob/d8ec3a3f6b02a8b941b484b3d254537af84b5fde/xarray/backends/common.py#L435

Stores each of our entrypoints like this: https://github.com/pydata/xarray/blob/d8ec3a3f6b02a8b941b484b3d254537af84b5fde/xarray/backends/h5netcdf_.py#L438

Then we append the local and other entrypoints together here: https://github.com/pydata/xarray/blob/d8ec3a3f6b02a8b941b484b3d254537af84b5fde/xarray/backends/plugins.py#L106-L116

But load_chunkmanagers doesn't really seem to append from a dict: https://github.com/pydata/xarray/blob/d8ec3a3f6b02a8b941b484b3d254537af84b5fde/xarray/core/parallelcompat.py#L48-L62

Why do the backends use the BACKEND_ENTRYPOINTS strategy? To avoid these cases? Or something else?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unrecognized chunk manager dask - must be one of: [] 1718410975
1556191288 https://github.com/pydata/xarray/issues/7856#issuecomment-1556191288 https://api.github.com/repos/pydata/xarray/issues/7856 IC_kwDOAMm_X85cwZg4 Illviljan 14371165 2023-05-21T14:17:30Z 2023-05-21T14:17:30Z MEMBER

The CI recreates its entire environment all the time and I don't?

```python from xarray.core.parallelcompat import list_chunkmanagers

list_chunkmanagers() Out[1]: {} ```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unrecognized chunk manager dask - must be one of: [] 1718410975
1556114932 https://github.com/pydata/xarray/issues/7856#issuecomment-1556114932 https://api.github.com/repos/pydata/xarray/issues/7856 IC_kwDOAMm_X85cwG30 Illviljan 14371165 2023-05-21T08:13:47Z 2023-05-21T08:13:47Z MEMBER

Our backends are stored in a dict like this: BACKEND_ENTRYPOINTS["h5netcdf"] = ("h5netcdf", H5netcdfBackendEntrypoint). Is it something similar daskmanager needs to do?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unrecognized chunk manager dask - must be one of: [] 1718410975
1556113793 https://github.com/pydata/xarray/issues/7856#issuecomment-1556113793 https://api.github.com/repos/pydata/xarray/issues/7856 IC_kwDOAMm_X85cwGmB Illviljan 14371165 2023-05-21T08:09:09Z 2023-05-21T08:09:09Z MEMBER

cc @TomNicholas 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unrecognized chunk manager dask - must be one of: [] 1718410975

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]);