issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 935279688 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 · 2 ✖

issue 1

  • conditionally disable bottleneck · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
897161325 https://github.com/pydata/xarray/pull/5560#issuecomment-897161325 https://api.github.com/repos/pydata/xarray/issues/5560 IC_kwDOAMm_X841eZht keewis 14808389 2021-08-11T21:18:05Z 2021-08-11T21:18:18Z MEMBER

I'm not sure how to test rolling: monkeypatching bottleneck.move_sum does not work because Rolling only accesses that on import, i.e. before the test is executed.

Everything else ~is~ should be done, though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   conditionally disable bottleneck 935279688
884359642 https://github.com/pydata/xarray/pull/5560#issuecomment-884359642 https://api.github.com/repos/pydata/xarray/issues/5560 IC_kwDOAMm_X840tkHa keewis 14808389 2021-07-21T17:23:45Z 2021-07-21T17:30:26Z MEMBER

as discussed in the meeting, we will keep use_bottleneck for now. I still don't know how to test this, but otherwise this should be ready for reviews and merging.

Edit: we also don't have alternatives for functions like duck_array_ops.push (used in ffill etc.) so disabling bottleneck would fail the function. Should we just silently use bottleneck, or raise an error?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   conditionally disable bottleneck 935279688

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