issue_comments

Table actions

5 rows where issue = 1250755592 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • dcherian · 5 ✖

issue 1

  • pre-release for v2022.06.0 · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1190471264 https://github.com/pydata/xarray/issues/6645#issuecomment-1190471264 https://api.github.com/repos/pydata/xarray/issues/6645 IC_kwDOAMm_X85G9SZg dcherian 2448579 2022-07-20T16:06:19Z 2022-07-20T16:06:19Z MEMBER

I'll issue the release once #6798 goes in.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pre-release for v2022.06.0 1250755592
1170445824 https://github.com/pydata/xarray/issues/6645#issuecomment-1170445824 https://api.github.com/repos/pydata/xarray/issues/6645 IC_kwDOAMm_X85Fw5YA dcherian 2448579 2022-06-29T20:08:01Z 2022-06-29T20:08:01Z MEMBER

I added pre-release install instructions to whats-new and scheduled a tweet for 45 minutes from now (giving RTD enough time to build)

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pre-release for v2022.06.0 1250755592
1143737346 https://github.com/pydata/xarray/issues/6645#issuecomment-1143737346 https://api.github.com/repos/pydata/xarray/issues/6645 IC_kwDOAMm_X85ELAwC dcherian 2448579 2022-06-01T15:12:11Z 2022-06-01T15:12:11Z MEMBER

Do we need to update whats-new.rst for this

👍🏾 It'd be nice to point to "known regressions" to prevent a bunch of duplicate bug reports.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pre-release for v2022.06.0 1250755592
1142395245 https://github.com/pydata/xarray/issues/6645#issuecomment-1142395245 https://api.github.com/repos/pydata/xarray/issues/6645 IC_kwDOAMm_X85EF5Ft dcherian 2448579 2022-05-31T17:07:02Z 2022-05-31T17:16:02Z MEMBER

The MVCE in #6607 does work on v2022.03.0. #6229 OTOH was broken earlier so technically not a regression

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pre-release for v2022.06.0 1250755592
1140134005 https://github.com/pydata/xarray/issues/6645#issuecomment-1140134005 https://api.github.com/repos/pydata/xarray/issues/6645 IC_kwDOAMm_X85D9RB1 dcherian 2448579 2022-05-28T01:50:06Z 2022-05-28T01:50:06Z MEMBER

Doing a pre-release sounds good to me.

But we know of at least three regressions (tagged under "release-blocker"). Should we fix them first?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pre-release for v2022.06.0 1250755592

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