issue_comments

Table actions

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

issue 1

  • Protect against an exception raised by python-eccodes · 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
817560437 https://github.com/pydata/xarray/pull/5139#issuecomment-817560437 https://api.github.com/repos/pydata/xarray/issues/5139 MDEyOklzc3VlQ29tbWVudDgxNzU2MDQzNw== alexamici 226037 2021-04-12T07:28:37Z 2021-04-12T07:28:37Z MEMBER

I'll merge it now to stop the CI from failing. The real fix is on the python-eccodes side: https://github.com/conda-forge/python-eccodes-feedstock/issues/69 and https://github.com/conda-forge/python-eccodes-feedstock/issues/71

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Protect against an exception raised by python-eccodes 855388231
817362317 https://github.com/pydata/xarray/pull/5139#issuecomment-817362317 https://api.github.com/repos/pydata/xarray/issues/5139 MDEyOklzc3VlQ29tbWVudDgxNzM2MjMxNw== keewis 14808389 2021-04-11T19:48:27Z 2021-04-11T19:48:55Z MEMBER

@andersy005, do you know of a way to skip running on push if pull_request is also run? Otherwise every PR opened from a branch on the main repository will have two CI runs.

Edit: would limiting push to master and maybe stable work?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Protect against an exception raised by python-eccodes 855388231
817360358 https://github.com/pydata/xarray/pull/5139#issuecomment-817360358 https://api.github.com/repos/pydata/xarray/issues/5139 MDEyOklzc3VlQ29tbWVudDgxNzM2MDM1OA== keewis 14808389 2021-04-11T19:33:26Z 2021-04-11T19:33:26Z MEMBER

looks good to me. Do you want to also pin eccodes temporarily? Otherwise the cfgrib tests will be skipped.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Protect against an exception raised by python-eccodes 855388231

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