issue_comments

Table actions

1 row where issue = 932898075 and user = 20629530 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

  • aulemahal · 1 ✖

issue 1

  • cftime 1.5.0 changes behviour upon pickling : breaks get_clean_interp_index with a dask distributed scheduler. · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
870748510 https://github.com/pydata/xarray/issues/5551#issuecomment-870748510 https://api.github.com/repos/pydata/xarray/issues/5551 MDEyOklzc3VlQ29tbWVudDg3MDc0ODUxMA== aulemahal 20629530 2021-06-29T16:35:02Z 2021-06-29T16:39:59Z CONTRIBUTOR

EDIT: I hit enter a bit too soon... I think I found the very source of the problem, maybe this could be fixed in cftime:

```python import pickle

ds.time # same No-Leap coordinate as in the MWE above

Items are instances of cftime.DatetimeNoLeap

pickle.loads(pickle.dumps(ds.time))

Items are instances of cftime.datetime, calendar information is now only an attribute, get_clean_interp_index will fail

```

However, as xarray has the possiblity to contain cftime coordinates where the calendar is an attribute, I guess get_clean_interp_index needs to be fixed?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cftime 1.5.0 changes behviour upon pickling : breaks get_clean_interp_index with a dask distributed scheduler. 932898075

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