issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 703881154 and user = 1312546 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

  • TomAugspurger · 3 ✖

issue 1

  • Fix optimize for chunked DataArray · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
694817581 https://github.com/pydata/xarray/pull/4432#issuecomment-694817581 https://api.github.com/repos/pydata/xarray/issues/4432 MDEyOklzc3VlQ29tbWVudDY5NDgxNzU4MQ== TomAugspurger 1312546 2020-09-18T11:36:49Z 2020-09-18T11:36:49Z MEMBER

I'm not sure, but I don't think so. It's strange that it didn't fail on the pull request.

On Thu, Sep 17, 2020 at 8:51 PM Maximilian Roos notifications@github.com wrote:

Might be best to proceed with #4434 https://github.com/pydata/xarray/pull/4434 for now. I'll need to give this a bit of thought.

OK, as you wish, I'll merge if that passes.

But your change did pass before the merge. Could it be a conflict (in functionality, not git) with recent changes on master?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/pull/4432#issuecomment-694601049, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKAOISNY5A5N2A44YR2ZMLSGK4JTANCNFSM4RQ6OP2Q . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix optimize for chunked DataArray 703881154
694594817 https://github.com/pydata/xarray/pull/4432#issuecomment-694594817 https://api.github.com/repos/pydata/xarray/issues/4432 MDEyOklzc3VlQ29tbWVudDY5NDU5NDgxNw== TomAugspurger 1312546 2020-09-18T01:27:30Z 2020-09-18T01:27:30Z MEMBER

Might be best to proceed with https://github.com/pydata/xarray/pull/4434 for now. I'll need to give this a bit of thought.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix optimize for chunked DataArray 703881154
694593225 https://github.com/pydata/xarray/pull/4432#issuecomment-694593225 https://api.github.com/repos/pydata/xarray/issues/4432 MDEyOklzc3VlQ29tbWVudDY5NDU5MzIyNQ== TomAugspurger 1312546 2020-09-18T01:22:43Z 2020-09-18T01:22:43Z MEMBER

Huh, I'm able to reproduce locally. Looking into it now.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix optimize for chunked DataArray 703881154

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