issue_comments

Table actions

2 rows where issue = 962467654 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • sel slice fails with cftime index when using dask.distributed client · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
894981650 https://github.com/pydata/xarray/issues/5677#issuecomment-894981650 https://api.github.com/repos/pydata/xarray/issues/5677 IC_kwDOAMm_X841WFYS aidanheerdegen 6063709 2021-08-09T06:30:26Z 2021-08-09T06:30:26Z CONTRIBUTOR

Thanks for the very prompt response @spencerkclark, the weekend intervened but I have since narrowed it down further so have submitted a new issue

https://github.com/pydata/xarray/issues/5686

Will close this one.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   sel slice fails with cftime index when using dask.distributed client 962467654
894211410 https://github.com/pydata/xarray/issues/5677#issuecomment-894211410 https://api.github.com/repos/pydata/xarray/issues/5677 IC_kwDOAMm_X841TJVS spencerkclark 6628425 2021-08-06T12:01:23Z 2021-08-06T12:01:23Z MEMBER

@aidanheerdegen thanks for the report. Are you sure that you are using cftime version 1.5.0? It is surprising to me that the dates are decoded to cftime.datetime objects and not cftime.DatetimeNoLeap objects. I suspect this is where the problem stems from -- currently xarray does not support the universal base class (https://github.com/pydata/xarray/issues/4853).

Eventually the goal is to deprecate the calendar-specific subclasses like cftime.DatetimeNoLeap. For a brief moment -- cftime version 1.4.0 -- the universal class was the default type returned by cftime.num2date, but this proved to be premature, because it broke a significant amount of downstream functionality. More recent versions -- 1.4.1 and later -- have rolled back to returning the subclasses by default. By any chance are you actually using version 1.4.0?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   sel slice fails with cftime index when using dask.distributed client 962467654

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