issue_comments

Table actions

4 rows where author_association = "NONE" and user = 13985417 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • gewitterblitz · 4 ✖

author_association 1

  • NONE · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1483473963 https://github.com/pydata/xarray/issues/7549#issuecomment-1483473963 https://api.github.com/repos/pydata/xarray/issues/7549 IC_kwDOAMm_X85YbAQr gewitterblitz 13985417 2023-03-24T21:58:38Z 2023-03-24T21:58:38Z NONE

Thanks, @trexfeathers. I had the same problem of HDF5 DIAG warnings after upgrading to xarray v2023.3.0 yesterday. Your diagnosis in SciTools/iris#5187 helped isolate the issue with libnetcdf v4.9.1. Downgrading libnetcdf to v4.8.1 resulted in no HDF5 warnings.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   HDF5-DIAG warnings calling `open_mfdataset` with more than `file_cache_maxsize` datasets (hdf5 1.12.2) 1596115847
1423154722 https://github.com/pydata/xarray/issues/2028#issuecomment-1423154722 https://api.github.com/repos/pydata/xarray/issues/2028 IC_kwDOAMm_X85U054i gewitterblitz 13985417 2023-02-08T19:47:22Z 2023-02-08T19:47:22Z NONE

Thanks, @benbovy. Yep, the kdtree objects don't like the range based slices. xoak has worked well in the past though. I'll keep an eye on xoak-xarray integration.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   slice using non-index coordinates 309691307
1422003293 https://github.com/pydata/xarray/issues/2028#issuecomment-1422003293 https://api.github.com/repos/pydata/xarray/issues/2028 IC_kwDOAMm_X85Uwgxd gewitterblitz 13985417 2023-02-08T04:52:23Z 2023-02-08T04:52:23Z NONE

Thanks @benbovy, it works well. I am curious about using set_xindex with 2-dimensional non-index coordinates. A use case could be datasets with x and y coordinates that need to be subset using longitude (x,y) and latitude (x,y) values. Any suggestions?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   slice using non-index coordinates 309691307
921926536 https://github.com/pydata/xarray/issues/2028#issuecomment-921926536 https://api.github.com/repos/pydata/xarray/issues/2028 IC_kwDOAMm_X84283uI gewitterblitz 13985417 2021-09-17T16:27:14Z 2021-09-17T16:31:55Z NONE

@dcherian any recoomendations for 2D non-dim coords?

I would like to subset a dataarray based on slices for x and y coordinates

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   slice using non-index coordinates 309691307

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