issue_comments

Table actions

2 rows where issue = 1315607023 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

  • xarray 2022.6.0 doesn't work well with numpy 1.20 · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1193164757 https://github.com/pydata/xarray/issues/6818#issuecomment-1193164757 https://api.github.com/repos/pydata/xarray/issues/6818 IC_kwDOAMm_X85HHj_V TomNicholas 35968931 2022-07-23T18:01:14Z 2022-07-23T18:01:14Z MEMBER

Right okay, thanks for the explanation @headtr1ck .

So either we do a version check for 1.20, or we create our own SupportsDType (I assume a Protocol?)

If we are still using a non-public interface, then we can't guarantee that it won't break again in numpy version 1.22 etc. So if that's the case perhaps we should try to make a sustainable solution. Otherwise I think special-casing one version is okay.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 2022.6.0 doesn't work well with numpy 1.20 1315607023
1193153124 https://github.com/pydata/xarray/issues/6818#issuecomment-1193153124 https://api.github.com/repos/pydata/xarray/issues/6818 IC_kwDOAMm_X85HHhJk TomNicholas 35968931 2022-07-23T16:42:28Z 2022-07-23T16:42:28Z MEMBER

What changed in numpy such that only one version is incompatible with our new release? Seems quite odd to have something break for one version, then work again for the next version.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray 2022.6.0 doesn't work well with numpy 1.20 1315607023

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