issue_comments

Table actions

4 rows where issue = 957131705 and user = 14808389 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

  • keewis · 4 ✖

issue 1

  • recent versions of sparse and dask seem to be incompatible with our tests · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
906487010 https://github.com/pydata/xarray/issues/5654#issuecomment-906487010 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X842B-Ti keewis 14808389 2021-08-26T14:57:13Z 2021-08-26T14:57:13Z MEMBER

Would it be possible to have the two issues tracked by separate tickets?

definitely, let's keep this one focused on sparse. I think removing the label should be enough to have CI open a new issue (not sure, though).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   recent versions of sparse and dask seem to be incompatible with our tests 957131705
903100279 https://github.com/pydata/xarray/issues/5654#issuecomment-903100279 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X8411Dd3 keewis 14808389 2021-08-21T11:07:49Z 2021-08-21T11:07:49Z MEMBER

FWIW, the upstream-dev CI installs sparse=0.12.0+55.ge706c2e (i.e. the most recent state of the repository). However, since our other CI is also failing I guess this does not change much.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   recent versions of sparse and dask seem to be incompatible with our tests 957131705
899874279 https://github.com/pydata/xarray/issues/5654#issuecomment-899874279 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X841ov3n keewis 14808389 2021-08-16T23:06:44Z 2021-08-17T10:57:50Z MEMBER

We already require pandas>=1.0 and I guess we can bump numpy (NEP29 allows it for releases after Jul 26), but I'm not sure why that would be an issue for the upstream-dev CI. For reference, the installed versions arenumpy=1.22.0.dev0+716.g20807c743 and pandas=1.4.0.dev0+436.gfcf3f24e02.

~Interestingly, the installation of dask from github started failing two days ago (see the last succeeding and the first failing install – unless I'm misinterpreting the logs?). Any idea how to fix that?~ The most recent run correctly installed dask so I guess this was a temporary issue (or dask resolved this really quickly)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   recent versions of sparse and dask seem to be incompatible with our tests 957131705
890406358 https://github.com/pydata/xarray/issues/5654#issuecomment-890406358 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X841EoXW keewis 14808389 2021-07-31T21:35:09Z 2021-07-31T21:35:09Z MEMBER

this seems to be caused by changes to either dask or sparse, not sure which.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   recent versions of sparse and dask seem to be incompatible with our tests 957131705

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