issue_comments

Table actions

3 rows where issue = 1474717029 and user = 14808389 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

  • keewis · 3 ✖

issue 1

  • Add python 3.11 to CI · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1400251477 https://github.com/pydata/xarray/pull/7353#issuecomment-1400251477 https://api.github.com/repos/pydata/xarray/issues/7353 IC_kwDOAMm_X85TdiRV keewis 14808389 2023-01-23T12:18:39Z 2023-01-23T12:18:39Z MEMBER

It seemed cleaner to just open a separate PR, so we can use this one to change the python version of the other CI jobs.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add python 3.11 to CI 1474717029
1400156106 https://github.com/pydata/xarray/pull/7353#issuecomment-1400156106 https://api.github.com/repos/pydata/xarray/issues/7353 IC_kwDOAMm_X85TdK_K keewis 14808389 2023-01-23T10:59:08Z 2023-01-23T10:59:08Z MEMBER

The failing sparse tests when numba seem to be due to the environment containing sparse=0.3.1, which is a really old version of sparse (and the only one on conda-forge that does not depend on numba), so I'd say we don't really care? Especially since we're about to drop python=3.8.

We need to remove sparse from the python=3.11 environments anyways, since it is implemented using numba.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add python 3.11 to CI 1474717029
1400131518 https://github.com/pydata/xarray/pull/7353#issuecomment-1400131518 https://api.github.com/repos/pydata/xarray/issues/7353 IC_kwDOAMm_X85TdE-- keewis 14808389 2023-01-23T10:38:28Z 2023-01-23T10:42:10Z MEMBER

In the interest of moving this forward, should we use a separate environment file for the main CI with python=3.11 and move all the other environments once these issues have been resolved? Up to you if that would be done here or in a new PR should you want to use this one for the switch to a different default python version.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add python 3.11 to CI 1474717029

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