issue_comments

Table actions

1 row where issue = 114773593 and user = 6514690 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

  • albertotb · 1 ✖

issue 1

  • Feature request: only allow nearest-neighbor .sel for valid data (not NaN positions) · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1016260786 https://github.com/pydata/xarray/issues/644#issuecomment-1016260786 https://api.github.com/repos/pydata/xarray/issues/644 IC_kwDOAMm_X848kuiy albertotb 6514690 2022-01-19T09:47:15Z 2022-01-19T09:47:15Z NONE

I just want to +1 this issue since I'm having the exact same problem. It would be great if the .sel(method="nearest") could ignore NaNs as an option

 
{
    "total_count": 15,
    "+1": 15,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request: only allow nearest-neighbor .sel for valid data (not NaN positions) 114773593

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