issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 869180122 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • max-sixty · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
828145755 https://github.com/pydata/xarray/issues/5225#issuecomment-828145755 https://api.github.com/repos/pydata/xarray/issues/5225 MDEyOklzc3VlQ29tbWVudDgyODE0NTc1NQ== max-sixty 5635139 2021-04-28T05:04:19Z 2021-04-28T05:04:19Z MEMBER

Hi @JavierRuano — good to see you again!

This seems to be a dask issue, is that correct?

I'd be surprised if it's a python 3.7 vs 3.9 difference — are you sure that's the only change — are the dask & xarray versions the same?

Also — have a look at GitHub's docs on how to format code & tracebacks — we appreciate people posting issues — but it is easier to read them if they're formatted reasonably.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   python3.9 dask/array/slicing.py in slice_wrap_lists Don't yet support nd fancy indexing  869180122

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