issue_comments

Table actions

4 rows where issue = 774553196 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

author_association 2

issue 1

  • Xarray with cfgrib backend errors with .where() when drop=True · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
751745304 https://github.com/pydata/xarray/issues/4733#issuecomment-751745304 https://api.github.com/repos/pydata/xarray/issues/4733 MDEyOklzc3VlQ29tbWVudDc1MTc0NTMwNA== DanielAdriaansen 18426352 2020-12-28T15:14:34Z 2020-12-28T15:14:34Z CONTRIBUTOR

Looks like an effective way to fix the bug is in xarray itself, so I reopen the issue.

Thanks so much for the reply and the swift fix! Much appreciated @alexamici and thanks for the hard work getting GRIB engine support into Xarray!

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray with cfgrib backend errors with .where() when drop=True 774553196
751682827 https://github.com/pydata/xarray/issues/4733#issuecomment-751682827 https://api.github.com/repos/pydata/xarray/issues/4733 MDEyOklzc3VlQ29tbWVudDc1MTY4MjgyNw== alexamici 226037 2020-12-28T11:34:22Z 2020-12-28T11:34:22Z MEMBER

Looks like an effective way to fix the bug is in xarray itself, so I reopen the issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray with cfgrib backend errors with .where() when drop=True 774553196
751232371 https://github.com/pydata/xarray/issues/4733#issuecomment-751232371 https://api.github.com/repos/pydata/xarray/issues/4733 MDEyOklzc3VlQ29tbWVudDc1MTIzMjM3MQ== alexamici 226037 2020-12-25T10:58:58Z 2020-12-25T10:58:58Z MEMBER

@DanielAdriaansen thanks for reporting, this is a duplicate of https://github.com/ecmwf/cfgrib/issues/157 so I'm going to close this one, and you can follow there.

I'm a bit embarrassed as @aurghs identified this bug a while back, but I forgot about it!

The fix should be easy, I'll try to make a release shortly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray with cfgrib backend errors with .where() when drop=True 774553196
750994231 https://github.com/pydata/xarray/issues/4733#issuecomment-750994231 https://api.github.com/repos/pydata/xarray/issues/4733 MDEyOklzc3VlQ29tbWVudDc1MDk5NDIzMQ== DanielAdriaansen 18426352 2020-12-24T20:30:18Z 2020-12-24T20:30:18Z CONTRIBUTOR

Paging @alexamici?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray with cfgrib backend errors with .where() when drop=True 774553196

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