issue_comments

Table actions

3 rows where issue = 818059250 and user = 2448579 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

  • dcherian · 3 ✖

issue 1

  • Automatic duck array testing - reductions · 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
1204086247 https://github.com/pydata/xarray/pull/4972#issuecomment-1204086247 https://api.github.com/repos/pydata/xarray/issues/4972 IC_kwDOAMm_X85HxOXn dcherian 2448579 2022-08-03T15:15:34Z 2022-08-03T15:15:34Z MEMBER

I also wonder whether we should have a separate job for hypothesis: this makes CI run quite a bit longer (about 70s on my machine just for sparse and pint reduce tests, which are a small part of the API)

Sounds good to me!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Automatic duck array testing - reductions 818059250
1192996302 https://github.com/pydata/xarray/pull/4972#issuecomment-1192996302 https://api.github.com/repos/pydata/xarray/issues/4972 IC_kwDOAMm_X85HG63O dcherian 2448579 2022-07-22T23:10:11Z 2022-07-23T02:09:12Z MEMBER

sparse seems to have different dtype casting behavior (it casts e.g. a mean of float16 to float64, while numpy stays at float16), so I'll need to figure out how to work around that.

Sparse doesn't support float16

~The remaining local failure is https://github.com/pydata/xarray/issues/6817 (perhaps we should run numpy tests too ;) )~

Failure is https://github.com/pydata/sparse/issues/553

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Automatic duck array testing - reductions 818059250
977446461 https://github.com/pydata/xarray/pull/4972#issuecomment-977446461 https://api.github.com/repos/pydata/xarray/issues/4972 IC_kwDOAMm_X846QqY9 dcherian 2448579 2021-11-24T02:44:00Z 2021-11-24T02:44:00Z MEMBER

The pint tests pass so all that's left is to figure out how to fix the sparse tests.

Can we xfail these new tests and merge for now? As long as tests/test_sparse.py still passes, there are no issues, correct?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Automatic duck array testing - reductions 818059250

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