issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 1382753751 and user = 35968931 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

  • TomNicholas · 2 ✖

issue 1

  • release? · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1261323979 https://github.com/pydata/xarray/issues/7069#issuecomment-1261323979 https://api.github.com/repos/pydata/xarray/issues/7069 IC_kwDOAMm_X85LLkbL TomNicholas 35968931 2022-09-28T18:43:06Z 2022-09-28T18:43:06Z MEMBER

Should we wait to fix any of the other regressions? Or just fix them in the next release.

Are we doing any kind of announcement about indexes with this release? Or just summarise whatsnew as normal?

Also kind of unrelated (I forgot to mention this in the meeting today) but can someone please add my columbia email (thomas dot nicholas at columbia dot edu)to the xarray dev team google group/list? I think it was attached to my old institutional address which has since lapsed.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   release? 1382753751
1255549756 https://github.com/pydata/xarray/issues/7069#issuecomment-1255549756 https://api.github.com/repos/pydata/xarray/issues/7069 IC_kwDOAMm_X85K1is8 TomNicholas 35968931 2022-09-22T21:08:12Z 2022-09-22T21:08:12Z MEMBER

It would be nice to be able to go back to what we were doing recently, i.e. releasing every 2 weeks (after each dev meeting). Will we be able to go back to that schedule after this release?

(I can release this next version too)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   release? 1382753751

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