issue_comments

Table actions

4 rows where issue = 1214654475 and user = 5635139 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 1

  • max-sixty · 4 ✖

issue 1

  • Opening a grib file leaves a .idx in the directory · 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
1109450011 https://github.com/pydata/xarray/issues/6512#issuecomment-1109450011 https://api.github.com/repos/pydata/xarray/issues/6512 IC_kwDOAMm_X85CIN0b max-sixty 5635139 2022-04-26T07:33:37Z 2022-04-26T07:33:37Z MEMBER

Cool, if you think we should document it better (or write to a temp file by default, less surprising perhaps?), then that's great, let's add the issue; it doesn't have to be you who implements.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opening a grib file leaves a .idx in the directory 1214654475
1109402183 https://github.com/pydata/xarray/issues/6512#issuecomment-1109402183 https://api.github.com/repos/pydata/xarray/issues/6512 IC_kwDOAMm_X85CICJH max-sixty 5635139 2022-04-26T06:33:37Z 2022-04-26T06:33:37Z MEMBER

Should we by default use a temp file? or is there some benefit to retaining the index file locally? (asking as someone with very little context{

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opening a grib file leaves a .idx in the directory 1214654475
1109284506 https://github.com/pydata/xarray/issues/6512#issuecomment-1109284506 https://api.github.com/repos/pydata/xarray/issues/6512 IC_kwDOAMm_X85CHlaa max-sixty 5635139 2022-04-26T03:42:27Z 2022-04-26T03:42:27Z MEMBER

I can repro, thanks @isodrosotherm .

It looks like we're passing this through to cfgrib.open_file: https://github.com/pydata/xarray/blob/main/xarray/backends/cfgrib_.py#L118.

Is this an xarray issue though? Or should upstream be cleaning up that file, assuming it should be cleaned up?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opening a grib file leaves a .idx in the directory 1214654475
1108915557 https://github.com/pydata/xarray/issues/6512#issuecomment-1108915557 https://api.github.com/repos/pydata/xarray/issues/6512 IC_kwDOAMm_X85CGLVl max-sixty 5635139 2022-04-25T18:44:24Z 2022-04-25T18:44:24Z MEMBER

Please could you confirm on the latest release of xarray, include the xr.show_versions(), and a MCVE?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opening a grib file leaves a .idx in the directory 1214654475

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