issue_comments

Table actions

4 rows where author_association = "CONTRIBUTOR" and user = 10580038 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)

user 1

  • antarcticrainforest · 4 ✖

author_association 1

  • CONTRIBUTOR · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1035103697 https://github.com/pydata/xarray/pull/6249#issuecomment-1035103697 https://api.github.com/repos/pydata/xarray/issues/6249 IC_kwDOAMm_X849sm3R antarcticrainforest 10580038 2022-02-10T16:08:43Z 2022-02-10T16:08:43Z CONTRIBUTOR

Thanks @antarcticrainforest! I think this may be the best we can do in terms of a solution for now.

It's great that you added an integration test using distributed, since we've had issues like this crop up before. Maybe you could also add a pickling test within test_cftimeindex.py similar to @mathause's example, and a what's new entry as well?

Okidoke I've added a test for pickling cftimeindex objects and updated the whats-new document. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix pickling issue 1125747268
1031362509 https://github.com/pydata/xarray/pull/6249#issuecomment-1031362509 https://api.github.com/repos/pydata/xarray/issues/6249 IC_kwDOAMm_X849eVfN antarcticrainforest 10580038 2022-02-07T11:28:03Z 2022-02-07T11:28:03Z CONTRIBUTOR

Any idea why the pipeline is broken ?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix pickling issue 1125747268
1026754743 https://github.com/pydata/xarray/issues/6226#issuecomment-1026754743 https://api.github.com/repos/pydata/xarray/issues/6226 IC_kwDOAMm_X849Mwi3 antarcticrainforest 10580038 2022-02-01T11:43:21Z 2022-02-01T11:44:32Z CONTRIBUTOR

Are we expecting the CFTimeIndex object to always have "O" as dtype? If so the solution would be straight forward. Which means I can create a PR.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_mfdataset fails with cftime index when using parallel and dask delayed client 1120276279
1026656699 https://github.com/pydata/xarray/issues/6226#issuecomment-1026656699 https://api.github.com/repos/pydata/xarray/issues/6226 IC_kwDOAMm_X849MYm7 antarcticrainforest 10580038 2022-02-01T09:52:39Z 2022-02-01T09:52:39Z CONTRIBUTOR

I just ran into the very same issue. Are you sure that this is a problem with pandas? I've had a look into the pandas changes between 1.3.X and 1.4.X. Apparently the _new_Index method, which gets involved when serialising the index object, has been changed:

elif "dtype" not in d and "data" in d: # Prevent Index.__new__ from conducting inference; # "data" key not in RangeIndex d["dtype"] = d["data"].dtype return cls.__new__(cls, **d)

the problem is, that __new__ doesn't except a dtype argument. I've tried adding a dtype argument and it works. So I guess since this class inherits from pd.Index it needs to be updated?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_mfdataset fails with cftime index when using parallel and dask delayed client 1120276279

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